Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Karthikeyan
    @karthikeayan
    @vishagilityroots I see you have done some work related to Jenkins box, can you tell us how is different from the jenkins box which is there in "app.vagrantup.com"
    ?
    Vishwanath Venugopalakrishnan
    @vishagilityroots
    @anadimisra uh-oh, I can hear the knives being sharpened :worried:
    Anadi Misra
    @anadimisra
    you could say Atom vs Sublime Text or Ruby vs Python perhaps
    Karthikeyan
    @karthikeayan
    no vim, no emacs.. vi is best :D no atom, no sublime.. vscode is best :D
    Anadi Misra
    @anadimisra
    @karthikeayan vscode rocks yeah I admit .... in the New kids on block
    Vishwanath Venugopalakrishnan
    @vishagilityroots

    can you tell us how is different from the jenkins box

    Basically its a plain vanilla Jenkins box where we have a little bit more control of versioning, packaging etc. We needed a box that we developed, which would reside in our repo, to be used in our Infra as Code projects, DevOps workshops etc. so we wrote that one.

    For example, there are other projects that take this box, then auto-configure Jenkins on top of it. So that Jenkins box acts as a base box for other projects, makes sense?

    You see a box ubuntu1604-base right? We could have used the box from vagrantup.com but again, we needed a measure of control over what goes into our base box. Hence a custom Ubuntu box.
    Karthikeyan
    @karthikeayan
    yeah, making sense.. basically Vagrantfile and puppet modules for each app.. Am I right?
    Vishwanath Venugopalakrishnan
    @vishagilityroots
    yep - with as much reusability as possible
    (and since I am always a Puppet learner, there's not too much reusability :) )
    :point_up: I can see you'd be a great person to help me improve my puppet knowledge btw
    Karthikeyan
    @karthikeayan
    sure, let me find some good time to join the project
    Vishwanath Venugopalakrishnan
    @vishagilityroots
    for now, the best help we can get is if you (and all of us here) can try the code out ... let us know if something doesn't work, log bug reports, find problems with documentation. That also won't take up too much of your time, I know we all have day jobs too ;)
    Lezz Giles
    @lezzgiles
    Sorry you're all wrong. vi is ok, vim is better, emacs better still, but the one that rules them all is ed.
    Anadi Misra
    @anadimisra
    ouch! yeah never tried ed though ☺
    welcome to the channel @lezzgiles
    Vishwanath Venugopalakrishnan
    @vishagilityroots
    vscode looks a lot like atom .. maybe it uses the electron framework as well. Love the color theme
    Vishwanath Venugopalakrishnan
    @vishagilityroots

    anyone get a chance to look at the vagrant boxes?

    vagrant-toolchains: Git repository with reusable DevOps environments

    Even though it's early days yet, I thought I'd point you guys out to this repo we have been working on:
    https://github.com/agilityroots/vagrant-toolchains

    Often I have encountered situations where I need a quick easy-to-create DevOps environment on my machine, that just works without any fuss. Several of my colleagues in recent assignments expressed the same need. As a result, we started working on these vagrant-based environments.

    In case you don't know what Vagrant is, this is a good document. We are working on some getting-started videos and docs in the mean time.

    Check out the repository and let me know if you need help figuring things out.

    anilkeshavamurthy
    @anilkeshavamurthy
    are you guys aware of any Jenkins plug-in which downloads artifact from artifactory/nexus only if it has changed, else it should take the cached artifact for deployment.
    Vishwanath Venugopalakrishnan
    @vishagilityroots
    @anilkeshavamurthy each nexus artifact is uniquely versioned, so each artifact would be unique ("changed"), no?
    guess some more explanation is needed
    anilkeshavamurthy
    @anilkeshavamurthy
    ok. lets say there are few jars which have not changed, so while building, instead of downloading all jars i want jenkins to exclude those jars so that build time can be optimized
    Anadi Misra
    @anadimisra
    do you need Jenkins to figure out his version change for Snapshot Versions?
    if you're using a maven or Gradle build based job their client libraries will take care of that
    Vishwanath Venugopalakrishnan
    @vishagilityroots

    if you're using a maven or Gradle

    yep was gonna say that. If you have 3 libs, log4j 1.2, foo 1.5 and bar 1.6... and if log4j 1.2 is already present in the build machine's M2 cache, Maven will not download it.

    anilkeshavamurthy
    @anilkeshavamurthy
    ok will explore that Thanks for the suggestion
    Vishwanath Venugopalakrishnan
    @vishagilityroots
    How're you doing folks? Thanks for recommending VSCode to me, it's awesome!
    Karthikeyan
    @karthikeayan
    @vishagilityroots try "Beautify" extension. my favourite
    Vishwanath Venugopalakrishnan
    @vishagilityroots
    How are you doing folks? We launched our new website recently. Watch the website for articles on DevOps. Let us know if you'd like coverage on any specific topics. www.agilityroots.com
    Karthikeyan
    @karthikeayan
    @vishagilityroots , good start..
    couldn't actively contribute bcoz of some office stuffs..
    Apoorv Garg
    @apoorv007
    Hi folks, good to join this room. Can we talk about the biggest pain points of the current monitoring tools faced by everyone here. Is it alert noise... finding root cause of the alert event...etc.
    Vishwanath Venugopalakrishnan
    @vishagilityroots
    @apoorv007 welcome! Good topic. Why don't you begin, what kind of pain points have you faced with monitoring tools?
    Vishwanath Venugopalakrishnan
    @vishagilityroots
    How about a symptom to begin with? I've noticed cases where there are so many notifications from Nagios or whatever, that team autofiltered it into a folder. In the name of "avoiding clutter".
    Karthikeyan
    @karthikeayan
    the tools which we are using is not real time..
    password expiry
    Vishwanath Venugopalakrishnan
    @vishagilityroots
    @karthikeayan does that mean you don't have monitoring? Didn't get you.
    Wishing everyone who is in India {and has a holiday tomorrow) a happy long weekend :)
    Apoorv Garg
    @apoorv007
    I agree with @vishagilityroots. Cause analysis is a manual process right now, but before that, getting a noise free signal of symptoms would help. I wonder if there is any tool out there to batch these notifications into one incident - a simple example - my apache web server could be affected by a sluggish database - can any tool automatically club the two alarms into one incident? Such batching could probably then be used to rank incidents by the impact they have (# of services affected)
    Vishwanath Venugopalakrishnan
    @vishagilityroots

    @apoorv007 an interesting thought -- since the cause is rarely one tool it makes sense to do this. OTMH I'm thinking of some smart visualization on the kibana side (assuming ELK here of course).

    • Perhaps events originating from the same toolstack (apache, mysql) could be 'tagged' or 'labelled' a certain way.
    • Kibana queries all events tagged a certain way and organizes them by label

    Thoughts?

    Apoorv Garg
    @apoorv007

    That could work. I am wondering what would be the size of a bucket of tools with the same tag? Too big or too small would imply noise. How often it would change; will it be a maintenance nightmare as the infra scales?

    I think the monitoring tools are better positioned to do such a batching since they have the information of which service is interacting at what point of time with which other service.

    Vishwanath Venugopalakrishnan
    @vishagilityroots

    Like all other DevOps infrastructure, your monitoring infrastructure cannot be "fire and forget" - it needs to be developed like any other software.
    In the context of monitoring this means continually evaluating whether you are giving

    • the right feedback,
    • the right kind of feedback, and
    • the right amount of it.

    So the solution here lies outside the choice of tools, and really is decided upon the practices surrounding those tools.

    Vishwanath Venugopalakrishnan
    @vishagilityroots
    Hello DevOps community, a couple of questions for you :
    Anadi Misra
    @anadimisra
    hi! all
    here's a Git repository WIP about simple coding katas using TDD
    I realised a lot of times we are creating more than just single script automation, there are modules & libraries etc that we end up writing for complex pipeline integration, and knowing the right way to code would be very helpful
    Srini555
    @Srini555
    Hi all