08-19-2016
Stomp has made some very true remarks here. I'd like to add some points.
1) Most questions in IT are not about the tools to use but about planning and "strategic coherence". If you solve problems without having an overlaying strategic decision made chances are you end up with a (in a way running but) quite incomprehensible environment. This will at some point come to haunt you and - unfortunately - not immediately but in the long run, when it is hard to redesign. So plan, plan thoroughly and then rethink your plans. You will get the invested time and effort back in manifolds.
2) stomp already mentioned it, but i'd like to stress the point for emphasis: keep in mind that your environment will change over time and that means you need a tool with enough flexibility and compatibility to support these ever-changing platforms. We are right now starting to use chef too to manage our AIX environment, btw. but are not completely satisfied because we need to use a Linux system as a chef server instead of our native platform.
3) Never forget that practice and prospects are two fundamentally different things. I grew up in a time when PC networks were nearly exclusively served by Novell Netware servers. Then came M$$ and shoved their "WinNT server" onto the market, usually against the outcry of the IT department. Their selling argument was like see, it looks like the Windows desktop your secretary uses to type your correspondence, so she can administrate your network in between two letters. This, of course was utter nonsense (my kitchen knife has the same "interface" as a scalpel - that doesn't qualify me as a surgeon), but it sounded good in the presentation. Once (that was back ~1993) the single 64MB 2-processor Novell server was thrown out and replaced by 8(!) 256MB-4-processor WinNT-Servers (which combined produced about half the speed of the single server before) it was too late to change directions. You might want to avoid such decisions.
4) If you can rely on open source tools. On average (notice: if you look at a specific product you need to evaluate it specifically, not on some market average which may or may not apply in the specific case) they are usually better maintained than commercial software and are less prone to falling victim to "strategic market decisions" - forcing customers to do the manufacturers bidding, no matter what. OSS development directions are (again: in general) also not driven by the same rationale as commercial software. Commercial software is built to earn money for the manufacturer, the more the better. Things like usability, fitness for a certain purpose and code quality are just means to this end, not goals themselves. With OSS software, which is in most cases written by volunteers for the sheer fun of it, this is different.
OK, so far. I might add more points after thinking this over.
I hope this helps.
bakunin
7 More Discussions You Might Find Interesting
1. Debian
Is there a way to configure the gnome file manager to open each directory in the same window instead of opening a new one? (Debian 5.0.0) (5 Replies)
Discussion started by: snorkack59
5 Replies
2. Solaris
Can somebody kindly help me to determine which one i should choose to better manipulate OS volume.
RAID manager or veritas volume manager?
Any critical differences between those two?
Thanks in advance. (5 Replies)
Discussion started by: beginningDBA
5 Replies
3. Solaris
hi all
i am a newbie to solaris and i am doing some R&D in veritas volume manager. This is my first day with veritas. I downloaded and installed Veritas storage foundation 5.1 package in my sun solaris 5.10 sparc machine. When i try to create disk group in vxvm, it giving one error message. I am... (6 Replies)
Discussion started by: kingston
6 Replies
4. Solaris
Hello,
There once was a disk. Veritas thought it wasn't happy, but it really was.
The disk was all alone on a plex. There was another plex, in the same volume, that was fine and happy with its own single disk.
I removed the plex with the unhappy disk. Then I went into vxdiskadm, removed... (2 Replies)
Discussion started by: kity1kity
2 Replies
5. Filesystems, Disks and Memory
In Sun manuals, I didn't find how to backup Sun StorageTek Common Array Manager's configuration. Is there a way to do it like backing up Brocade switch configuration? CAM is under Solaris 10.
Thank you in advance! (0 Replies)
Discussion started by: aixlover
0 Replies
6. Red Hat
HI,
I use red hat linux ES 5.
I start the virt-manager and add new guest host in it .
But When I choose parXXX-virtuXXXXX ...not full-virtXXXx...
I get below screen to fill
installtion source
Please indicate where installation media is available
for the operating system you would like to... (1 Reply)
Discussion started by: chuikingman
1 Replies
7. UNIX for Advanced & Expert Users
Hello Dears,
I am up to install configuration manager as the number of Linux systems are growing alot in my company.
can please advise any of them?
Puppet, spicewalk ansilble etc.. please share you opinion.
My aim is to have config manager to automate/provision systems and to have inventory... (1 Reply)
Discussion started by: Vit0_Corleone
1 Replies
LEARN ABOUT DEBIAN
knife-configure
KNIFE-CONFIGURE(1) Chef Manual KNIFE-CONFIGURE(1)
NAME
knife-configure - Generate configuration files for knife or Chef Client
SYNOPSIS
knife configure [client] (options)
DESCRIPTION
Generates a knife.rb configuration file interactively. When given the --initial option, also creates a new administrative user.
CONFIGURE SUBCOMMANDS
knife configure (options)
-i, --initial
Create an initial API Client
-r, --repository REPO
The path to your chef-repo
Create a configuration file for knife. This will prompt for values to enter into the file. Default values are listed in square brackets if
no other entry is typed. See knife(1) for a description of configuration options.
knife configure client directory
Read the knife.rb config file and generate a config file suitable for use in /etc/chef/client.rb and copy the validation certificate into
the specified directory.
EXAMPLES
o On a freshly installed Chef Server, use knife configure -i to create an administrator and knife configuration file. Leave the field
blank to accept the default value. On most systems, the default values are acceptable.
user@host$ knife configure -i
Please enter the chef server URL: [http://localhost:4000]
Please enter a clientname for the new client: [username]
Please enter the existing admin clientname: [chef-webui]
Please enter the location of the existing admin client's private key: [/etc/chef/webui.pem]
Please enter the validation clientname: [chef-validator]
Please enter the location of the validation key: [/etc/chef/validation.pem]
Please enter the path to a chef repository (or leave blank):
Creating initial API user...
Created (or updated) client[username]
Configuration file written to /home/username/.chef/knife.rb
This creates a new administrator client named username, writes a configuration file to /home/username/.chef/knife.rb, and the private
key to /home/username/.chef/username.pem. The configuration file and private key may be copied to another system to facilitate adminis-
tration of the Chef Server from a remote system. Depending on the value given for the Chef Server URL, you may need to modify that set-
ting after copying to a remote host.
SEE ALSO
knife(1) knife-client(1)
AUTHOR
Chef was written by Adam Jacob adam@opscode.com with many contributions from the community.
DOCUMENTATION
This manual page was written by Joshua Timberman joshua@opscode.com. Permission is granted to copy, distribute and / or modify this docu-
ment under the terms of the Apache 2.0 License.
CHEF
Knife is distributed with Chef. http://wiki.opscode.com/display/chef/Home
Chef 10.12.0 June 2012 KNIFE-CONFIGURE(1)