Archive for configuration

[just.few.tuts] Puppet ~ Beginner’s Concept Guide (Part 4) Where Is My Data?

Posted in Blogroll, tutorial with tags , , , , , , , , , , , , , , , on August 2, 2013 by abhishekkr

justfewtuts.blogspot.in [26/July/2013]

http://justfewtuts.blogspot.com/2013/07/wip-puppet-beginners-concept-guide-part.html

Puppet
beginners concept guide (Part 4)

Where is my Data?

When I started my Puppet-ry, the examples I used to see had all configuration data buried inside the DSL code of manifests, people were trying to use inheritance to push down data. Then got to see a design pattern in puppet manifests keeping out separate parameters manifest for configuration variables. Then came along the External Data lookup via CSV files as a Puppet function. Then with enhancements in puppet and other modules came along more.

Below are few usable to fine ways utilizing separate data sources within your manifests,

Here, we will see usage styles of data for Puppet Manifests, Extlookup CSV, Hiera, Plug-in Facts and PuppetDB.

params-manifest:

It is the very basic way of separating out data from your functionality code, and the preferred way for in-future growing value-set type of data. It will keep it separate from the code since start.

…..

…..click here to read full post

[just.few.tuts] Testing Chaos with Automated Configuration Management solutions

Posted in Blogroll, tutorial with tags , , , , , , , , , , , , , , , , , on June 23, 2013 by abhishekkr

justfewtuts.blogspot.in [31/May/2013]

http://justfewtuts.blogspot.in/2013/05/testing-chaos-with-automated.html

…..That’s the shift. The logic developed for Infrastructure acts as a glue to all other applications created in house and 3rd party. Here in Infrastructure feature development there is more to test for the effect it has on the it’s users (software/hardware) and less on internal changes (dependencies and dynamic content). Now the stuff in parentheses here means a lot more than seems… let’s get into detail of it.

Real usability of Testing is based on keeping sanctity of WHAT needs to be tested WHERE.

Software/Hardware services that collaborate with the help of Automated Infrastructure logic needs major focus of testing. These services can be varying from the
  • in-house ‘Product’, that is the central component you are developing
  • 3rd Party services it collaborates with,
  • external services it utilizes for what it doesn’t host,
  • operating system that it supports and Ops-knows what not.
Internal changes mainly revolve around
  • Resources/Dependencies getting called in right order and grouped for specific state.
  • It also relates to correct generation/purging of dynamic content, that content can itself range as
    • non-corrupt configuration files generated of a template
    • format of sent configuration data from one Infra-component to another for reflected changes
    • dynamically creating/destroying service instances in case of auto-scalable infrastructure

One can decide HOW, on ease and efficiency basis.

Unit Tests work for the major portion of ‘Internal Changes’ mentioned before usingchefspecrspec-chefrspec-puppet like libraries are good enough. They can very well test the dependency order and grouping management…..

…..click here for full blogpost

[tekwalk] Apache httpd VirtualHosts : one gets default, unknown faults

Posted in Blogroll, tutorial with tags , , , , , , , on April 30, 2013 by abhishekkr

tekwalk.blogspot.com [13/Jan/2013]

http://tekwalk.blogspot.in/2013/01/apache-httpd-virtualhosts-one-gets.html

Recently faced a situation where even after removing a VirtualHost, its ServerName was giving HTTP 200 response. It was all because of missed RTFM agenda.

When VirtualHosts get applied in Apache HTTPD server configuration, the first definition encountered by Apache Controller gets selected as the default route logic selected if the ServerName doesn’t match any provided.

example scripts at https://gist.github.com/abhishekkr/4526414

…click here to read full post

[just.few.tuts] Puppet ~ Beginners Concept Guide [Part#3] :: Modules much more

Posted in AbhishekKr, Blogroll, tutorial with tags , , , , , , , , , on September 1, 2012 by abhishekkr

justfewtuts.blogspot.in [5/August/2012]

http://justfewtuts.blogspot.in/2012/08/puppet-beginners-concept-guide-part-3.html

MODULES WITH MORE

here some time on the practices to prefer while writing most of your modules

[] HowTo Write Good Puppet Modules  
(so everyone could use it and you could use it everywhere)

  • platform-agnostic
    With change in Operating System …..
  • untangled puppet strings
    You are…..
  • no data in c~o~d~e
    Now when you are…..
  • puppet-lint
    To keep the …..
  • do-undo-redo
    It’s suggested to …..

[] More about Modules  (moreover…..)
Where to get…..

…..click here to read full post

[just.few.tuts] DevOps AND 12FactorApp ~ some obsolete & much valid

Posted in Uncategorized with tags , , , , , , , , , , , , , , , , , on August 21, 2012 by abhishekkr

justfewtuts.blogspot.in [28/July/2012]

http://justfewtuts.blogspot.in/2012/07/devops-and-12factorapp-some-obsolete.html

What?

Actually what 12FactorApp is… it is a good set of ideas around basic set of concerns. The concerns are right, the solutions suggested are situational and the situation is the default/basic setup. With the teams following good DevOps-y practices, they don’t turn out to be exactly same.

…..

What @12FactorApp doesn’t suit at all for DevOps-y Solutions

  1. ~
  2. Dependencies
    [+] Obsolete: ‘If the app needs to shell out to a system tool, that tool should be vendored into the app.’
    Changed-to: Make your automation configuration management system handle it.

…..

Cumulative Correct Concerns 3C@12FactorApp and DevOps-y Solutions

Overall aiming to achieve a easy-to-setup, clean-to-configure, quick-to-scaleand smooth-to-update software development ambiance.
The 12 Concerns+Solutions:

  1. Problem: Maintaining Application Source Code
    Solution:
    a.
     Using Version Control Mechanism, if possible Distributed VCS like git. Private hosted (at least private account) code repository.
    b. Unique application

…..

…..click here to read full post

[just-few-tuts] A Beginner’s Concept Guide for Puppet [part#1]

Posted in AbhishekKr, Blogroll, tutorial with tags , , , , , , , , , on July 10, 2012 by abhishekkr

justfewtuts.blogspot.in [29/May/2012]

http://justfewtuts.blogspot.in/2012/05/puppet-beginners-concept-guide-part-1.html

Puppet beginners concept guide (Part 1)
[] What  it  is?  When  is  it  required?  (for all new guys, who came here while just browsing internet)
Puppet is an…..

[] Quickie.
Install …..

[] Dumb  usage  structure.
Create…..

[] How  it  evolves?
Now, as any …..

…..click here to read full post

[tekwalk] [Puppet] Exported Resources is a beautiful thing….. thing to use and improvise

Posted in ABK Labs, Blogroll with tags , , , , , , on April 10, 2012 by abhishekkr

tekwalk.blogspot.com [14-March-2012]

http://tekwalk.blogspot.in/2012/03/puppet-exported-resources-is-beautiful.html

Lately, I’ve been real blunt towards Puppet because of the soup that leaked some specific scenario flaws in very busy times.
So, it’s my duty to applause if I like something which is a novel and beautiful concept.
For a well organized auto-magically managed set-up apart from a fine infrastructure and its configuration management mechanism, a very important part is for the monitoring and logging solution to spread across the infrastructure in a similar seamless and scalable fashion.
Puppet enables it very finely with the use of exporting and collecting resources.
Exported Resources are super virtual resources.
Once exported …..
…..click here to read full original post