Showing posts with label configuration. Show all posts
Showing posts with label configuration. Show all posts

Thursday, 21 April 2016

puppet Stages for Configuration Management

puppet has Two Stages for Configuration Management
Puppet configures systems in two main stages:

Compile a catalog
Apply the catalog
What is a Catalog?
A catalog is a document that describes the desired system state for one specific computer. It lists all of the resources that need to be managed, as well as any dependencies between those resources.

To compile a catalog, Puppet uses several sources of information. For more info, see the pages on

1) basics of the Puppet language
2) catalog compilation

puppet for manage the configuration

what is puppet.
Puppet is designed to manage the configuration of Unix-like and Microsoft Windows systems decoratively.
The user describes system resources and their state.
ref : wikipedia 
puppet is not a scripting language.
since we are changing the state of a resource.


Wednesday, 13 April 2016

security configuraton in jenkins

security configuraton in jenkins

1) click on manage jenkins

2) From the list of option choose "Configure Global Security".
this will allow user Secure "Jenkins" and  define who is allowed to access/use the system.

3) Click on Enable security
(If enabled, you have to login with a username and a password that has the "admin" role before changing the configuration)
options :
a) TCP port for JNLP slave agents
a.1) Jenkins uses a TCP port to communicate with slave agents launched via JNLP
a.2) Alternatively, you can specify the fixed port number so that you can configure your firewall accordingly.
a.3) Disable remember me : Select this option to remove the “Remember me on this computer” checkbox from the login screen.

4) Access Control
4.1) Security Realm
options :
a) Delegate to servlet container :  Use the servlet container to authenticate users, as per defined by the servlet spec.
b)  Jenkins’ own user database : Use Jenkins's own user list for authentication, instead of delegating that to an external system. for small system .
c)  LDAP :

5) Authorization
a) Anyone can do anything :
b) legacy mode
c) Logged-in users can do anything
d) Matrix-based security : In this scheme, you can configure who can do what by using a big table.
e) Project-based Matrix Authorization Strategy
(This allows you to say things like "Joe can access project A, B, and C but he can't see D." See the help of "Matrix-based security" for the concept of matrix-based security in general. ACLs are additive, so the access rights granted below will be effective for all the projects.)

6)
click on save  and will be redirected to signup page, provide the details and login