VCS on AIX

Special Forums UNIX and Linux Applications High Performance Computing VCS on AIX

05-20-2009

Moderator

869, 117

Join Date: May 2008

Last Activity: 3 June 2020, 5:57 PM EDT

Location: Lone Star State, USA

Posts: 869

Thanks Given: 26

Thanked 117 Times in 94 Posts

VCS on AIX

Hi,
is anybody here experienced in running VCS on AIX and happy to give me some advice regarding configuration questions?
I expect very high network IO on my cluster - so a single gig-e network will not be sufficient - and though I would like to configure more than one network card per node and implement some load balancing - but I am not yet entirely sure what would be the best solution to realize this.
Thanks and regards
zxmaus

zxmaus

View Public Profile for zxmaus

Find all posts by zxmaus

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

VCS not active

Dear All, My current system run Solaris 9 SPARC 64 bit , and VXVM , VCS 4.1. I check all the node information . ls -l /etc/vx/*.exclude /etc/vx/*.exclude: No such file or directory root@devuardbs01 # vxdctl license All features are available: Mirroring Root Mirroring Concatenation...

2. High Performance Computing

VCS install error

hai this is samiulla i am installing vcs 6.0 in vmware solaris 10 (64bit) i got error while i am going to install vcs in 2 nodes even i add rhost files on both nodes and ssh autho login still i got error. But i install vcs within one node it installs but when going to install in both nodes i got...

3. Solaris

VCS- question

Hi admins, I have a question on shared diskgroup in vcs. Let's say i have two node cluster node A and B. I am having the failover service group (including the required resources such as disk grp, IP, mount..etc) For an instance, the service grp is running on node A and suddenly if one of the...

4. Solaris

VCS on Solaris: VCS ERROR V-16-2-13077 (host2) Agent is unable to offline resource(DiskReservation)

hi, dear all I get a problem "VCS ERROR V-16-2-13077 " on VCS 4.1 for Solaris 10. I can not offline the host2 when the raid is bad. I don't know the reason and how to offline host2 and switch to host1. please help me, thank you! the message of engine_A.log is : ...

5. Solaris

VCS Clusters

:)Hi, can someone please explain VCS clustering and where do we need VCS clusters ..? :o:)Thanks in advance :o:)

6. Solaris

VCS for Solaris 32 bit OS

Hi Admins, I know that VCS supports Solaris x86-64bit only...and I need vcs for Solaris 32 bit-x86..running on vmware workstation.. I need to run vcs on vmware workstation...And my laptop support only 32bit... Please suggest.. Thanks..

7. UNIX for Dummies Questions & Answers

vcs agent

Hi all, I'm new to vcs. I have a doubt. I need to know, what will happen if an agent is stopped while reources being online. Eg.. while the oracle agent is stopped, will all the oracle resources will become offline.. Advanced thanks

8. Solaris

VCS heartbeat

we have a vcs cluster set up and noticed that they were showing one of the heart beat link qfe3 as DOWN. Both qfe2 and qfe3 were fine all along, btw if I were to push in/re-set the hb cable, do you know whether it will panic or cause anything to the system,? Its a DB critical prod nodes

9. High Performance Computing

What does the 'probe' do in VCS?

Weird question I know, but I'm intrigued. Say for instance you have an Application in an SG with the usual start/stop/monitor. To successfully probe does it just check for existence of the script/file ? Thanks...

10. Solaris

VCS Log

Hi All, Can anyone help me to analyse this VCS log. One of my applications failover suddenly and I need to find out the reason behind this. 2009/04/09 10:58:57 VCS ERROR V-16-2-13067 (CS49PAPS2) Agent is calling clean for resource(Web-ebill2app) because the resource became OFFLINE...

LEARN ABOUT DEBIAN

pkgkde-vcs

PKGKDE-VCS(1)						  Debian KDE packaging VCS helper					     PKGKDE-VCS(1)

NAME

       pkgkde-vcs - a helper tool for Debian pkg-kde VCS repositories.

SYNOPSIS

       pkgkde-vcs [-vy] subcommand [ SUBCOMMAND OPTIONS ] [ -- EXTERNAL TOOL OPTIONS ]

       pkgkde-git [-vy] subcommand [ SUBCOMMAND OPTIONS ] [ -- EXTERNAL TOOL OPTIONS ]

DESCRIPTION

       pkgkde-vcs is a helper tool which aims to simplify a couple of routine tasks associated with packaging management in version control system
       (VCS) repositories.  pkgkde-vcs transparently supports VCSes used by Debian Qt/KDE maintainer groups wrapping various VCS  related  command
       sequences  into	a  convenient CLI interface. Please note that this helper enforces the best practises and packaging conventions adopted by
       Debian Qt/KDE maintainer groups and therefore it should not be considered as a general purpose packaging helper.

       pkgkde-vcs should be run from the fully checked out packaging repository of the package it is supposed to act upon. Firstly, it attempts to
       detect  a  VCS  in  use for the particular packaging in the working directory. Please note, that the detection might fail if underlying VCS
       utilities are not installed. If you want or have to force a specific VCS type, run the command as pkgkde-$vcs, for example pkgkde-git.

       If detection is successful, pkgkde-vcs will perform tasks as defined for the specified subcommand (e.g. tag). Different set of  subcommands
       might  be  defined  for	each VCS and each of them might accept a different set of SUBCOMMAND OPTIONS (see below). All locally unrecognized
       subcommand options (or the ones specified as EXTERNAL TOOL OPTIONS after --) will be passed to the external VCS	tool(s)  which	pkgkde-vcs
       executes to do the job.

       pkgkde-vcs  accepts  a  couple of common options which apply to the helper as whole or are common for all VCSes it supports. They should be
       passed before subcommand in order to be recognized.

       Even if pkgkde-vcs does extensive sanity checks before doing anything, an underlying command it executes might still fail. Then	pkgkde-vcs
       will terminate immediately possibly leaving repository in an inconsistent state. It is up to a user to recover from such a failure.

       At the moment, pkgkde-vcs supports only Git VCS.

OPTIONS

   Common options
       -y     By  default,  execution  of  the first external command that makes changes to the repository has to be explicitly confirmed by user.
	      However, if this option is specified, the first command will be run without confirmation.

       -n     Do not run any external commands that make changes to the repository. Useful with -v to see what commands with what options would be
	      run.

       -v     Be more verbose (e.g. show external commands as they are executed).

       -- EXTERNAL TOOL OPTIONS
	      Pass additional EXTERNAL TOOL OPTIONS to the external commands pkgkde-vcs executes to accomplish the task. See documentations of the
	      specific subcommand for more details.

SUPPORTED VERSION CONTROL SYSTEMS AND SUBCOMMANDS

   Git
       In order to use pkgkde-vcs with Git, git(1) must be available in PATH.  Bare Git repositories are not supported and Git	repository  should
       be in the fully checked out state (except clone). The following subcommands for Git repositories are supported at the moment:

       clone  Clone  the  specified  pkg-kde git repository. This subcommand should be specified by forcing VCS to git, i.e. by running pkgkde-git
	      command rather than pkgkde-vcs.

	      Repository should be specified relatively to the root of the official pkg-kde repository	tree.  Once  operation	is  complete,  the
	      cloned  repository  will be put at the same relative location on the local filesystem and update-config (see below) will be executed
	      on it.

	      For example, in order to clone kde4libs repository from kde-sc, akonadi repository from kde-req and  pkg-kde-tools  repository  from
	      the root tree, execute:

	      $ pkgkde-git clone kde-sc/kde4libs

	      $ pkgkde-git clone kde-req/akonadi

	      $ pkgkde-git clone pkg-kde-tools

       tag    Tag  current packaging state (HEAD) as upload to Debian archive. Repository working tree must be clean before executing this subcom-
	      mand. Current package version and target distribution are automatically determined from debian/changelog.  Distribution  must  be  a
	      valid Debian suite in order to avoid tagging of unfinished (aka UNRELEASED) revisions.

	      The  subcommand  will  create  an  annotated Git tag under "debian/" namespace. The subcommand itself does not accept any additional
	      options. All EXTERNAL TOOL OPTIONS (if specified) and will be passed to git tag invocation. It is recommended to sign tags by speci-
	      fying -s option.

	      The tag created by pkgkde-vcs tag will meet the following requirements:

	      o      The  tag  will named as "debian/<version>" where <version> is a full debian package version without epoch. All occurrences of
		     the ~ character in <version> will be replaced with the - character because Git does not support ~ character in tag names.

	      o      The tag will be assigned the message with content like <version>/<distribution>" where <version> is a full debian version	of
		     the package (without any modifications including epoch) and <distribution> is the distribution this package is uploaded.

	      For  example, a standard pkgkde-vcs tag will execute the following under the hood (assuming version is 1:2.3.4-5 and distribution is
	      experimental):

		     $ git tag debian/2.3.4-5 -m "1:2.3.4-5/experimental"

       update-config
	      Do some common configuration on the checked out packaging repository. At the moment, the subcommand performs the following:

	      o      Set up master branch and debian tags for pushing. -f option may be specified to force update  of  the  pushing  configuration
		     even if some pushing configuration already exists.

	      o      Set  repository user name and email address to the values of the DEBFULLNAME and DEBEMAIL environment variables respectively.
		     -f option may be specified to override the values even if the repository has some specified already.

LICENSE

       This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as  published	by
       the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

AUTHORS

       Modestas Vainius <modax@debian.org>

0.15								    2012-05-27							     PKGKDE-VCS(1)

High Performance Computing