chef-boneyard / devops-kungfu Goto Github PK

Chef Style DevOps Kung fu

License: MIT License

JavaScript 41.54% CSS 23.15% HTML 25.16% SCSS 10.15%

devops-kungfu's Introduction

Chef Style DevOps Kung fu

This repository defines Chef Style DevOps Kung fu.

It includes a presentation you can give, or ask people to watch, which explains what DevOps is, and defines a style of practice that comes from the lived experience of many DevOps professionals. It is a collaborative space, where all practitioners of the style can come together to create a reference for how to build up their own DevOps Kung fu, and teach others how to improve theirs.

You should start by watching the presentation, then come back here. If you agree with the fundamental principles, wish to practice our forms, and apply the style to your professional life, you can join our school by sending a pull request to this README file, and adding your name to the list of practitioners.

The slides are available online.

If you like most of what you see, but not all, or wish to emphasize different things about your style - but you agree on the same fundamental principles - you should fork this repository, remove the names of practitioners from this file, and found your own school of DevOps Kung fu. All we ask is that you please give attribution of your style as a derivative of Chef Style DevOps Kung fu.

What is DevOps?

A cultural and professional movement, focused on how we build and operate high velocity organizations, born from the experiences of its practitioners.

Practitioners of Chef Style DevOps

License

Chef Style DevOps Kung fu by Chef Software, Inc. is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. A full list of incorporated sources is included.

Based on reveal.js

Based on reveal.js.

Reveal.js is MIT licensed

devops-kungfu's People

Contributors

Stargazers

Watchers

Forkers

aweiker gkra kclair pudge josephrdsmith jmcgarr nathenharvey shashirsa 8x8cloud emagana-zz uchandrasekar mcoletti ncerny jcejohnson-archive ianatkin lnxchk pjudt rakutentech tonylovesdevops ozzyogkush wyrdvans nellshamrell spuder juliandunn ofross tomashley jaymzh cstewart87 veloandy smacfarlane chrisfarnham hansnqyr sbcas larrywright davecasey smith robbkidd sauraus rshade tjsoftworks err0 ubergeekgirl fujin bignastybryce toddmichael jefflaplante jaconstantine dromologue tekbuddha alexmanly ahpook mahirl khalavak pazel mbainter miketlive parthmonga davidschou cshlittle mfdii tfitch edgester kennonkwok soosiechoi benr jjasghar joshbrand teknofire fitsnips nickrycar swettk rx007 kforsthoevel jrnt30 adamleff desktophero gmiranda23 tknerr burtlo jakef chris-sanders-dot-org jgrill karobeck-zz vinyar tonynotto jbpadgett ducke rarenerd anfleene jmeinhorn crackmac wnthompson78 yvovandoorn slushpupie mattstratton xargs-p jhotta damacus mingderwang digitaljedi2

devops-kungfu's Issues

Hey

Is this project dead ?

I don't want to spend time to get this running if this project is not active.

I have the same problem as #266 (comment)

I am also following the Udacity course, so I tried to install it on Ubuntu 18.04 to fix it and it shows a lot of deprecated packages + stalls on

> [email protected] install /home/tricia/ecq/devops-kungfu/node_modules/node-sass
> node build.js

with no output.

Did I miss the opportunity to collab with the Chef community on DevOps kung-fu?

I was the 6th PR (a quick look, not scientific!) submitted to the kung-fu repo. I submitted a variation to the item in the Chef Tao around "scale" which was just sort of deleted.

https://github.com/chef/devops-kungfu/blob/b215f1ea71d58ff1ce74b741ac1c8bc6702ef225/index.html#L963

Is that enough of a variant to warrant a different fu or if there's a chance to have more convo/explanation on my perspective.

@adamhjk

Add James Johnson

Is there a discussion area?

So, I've got some questions on how Chef-Style DevOps Kung-Fu might apply in certain circumstances, such as within a professional services organization that is doing work for clients as opposed to product or SaaS development that could/should presumably be shareable with the entire company.

Should that discussion take place here on github somewhere, or is there a different location where that discussion should take place?

Updating talk-notes.md to more closely reflect the actual presentation?

So, I finished watching the video last night, and I got to looking at the talk-notes.md. Early on, there is a good deal of commonality between the talk as presented on the video versus the slides, but as you go further, there is more and more divergence in some areas. And some areas where there simply is no content at all in talk-notes.md relative to the video.

Should we be "correcting" talk-notes.md to more accurately reflect the presentation as it was given in the video? Should they be as presented in the video with further improvements/embellishments?

The readme instructions lead to an error.

I reached the point 3

If you want to run tests on the app -
In the VM run:
cd devops-kungfu
To install app specific node packages:
sudo npm install
Now you can run tests - grunt -v

but after the sudo npm install I get the following error.

Create a gh-pages branch to publish these slides

Github pages is awesome. If we create a gh-pages branch (from master) it will publish these slides to http://chef.github.io/devops-kungfu

`npm install` fails with error.

Describe the problem

sudo npm install leads to error messages.

Software Version

Master branch, Ubuntu 14.04.

Replication Case

I'm using the Udacity DevOps course setup. This consists of a packer Ubuntu image, VirtualBox and Vagrant.

Stacktrace

> [email protected] install /home/vagrant/devops-kung/node_modules/grunt-sass/node_modules/node-sass
> node build.js


/home/vagrant/devops-kung/node_modules/grunt-sass/node_modules/node-sass/node_modules/mocha/node_modules/debug/src/node.js:120
exports.inspectOpts = Object.keys(process.env).filter(key => {
                                                           ^
SyntaxError: Unexpected token >
    at Module._compile (module.js:439:25)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/home/vagrant/devops-kung/node_modules/grunt-sass/node_modules/node-sass/node_modules/mocha/node_modules/debug/src/index.js:9:19)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
npm ERR! Linux 4.4.0-142-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v0.10.48
npm ERR! npm  v2.15.1
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: `node build.js`
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the [email protected] install script 'node build.js'.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node build.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs node-sass
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/vagrant/devops-kung/npm-debug.log

Running the tests with grunt -v also yields errors.

/home/vagrant/devops-kung/node_modules/grunt-sass/tasks/sass.js:3
const util = require('util');
^^^^^
Loading "sass.js" tasks...ERROR
>> SyntaxError: Use of const in strict mode.
>>     at Module._compile (module.js:439:25)
>>     at Object.Module._extensions..js (module.js:474:10)
>>     at Module.load (module.js:356:32)
>>     at Function.Module._load (module.js:312:12)
>>     at Module.require (module.js:364:17)
>>     at require (module.js:380:17)
>>     at loadTask (/home/vagrant/devops-kung/node_modules/grunt/lib/grunt/task.js:323:10)
>>     at /home/vagrant/devops-kung/node_modules/grunt/lib/grunt/task.js:361:7
>>     at Array.forEach (native)
>>     at loadTasks (/home/vagrant/devops-kung/node_modules/grunt/lib/grunt/task.js:360:11)

Possible Solution

Specify correct dependencies in package.json.

Bug in availability formula

Availability = uptime/uptime+downtime
should probably be:
Availability = uptime/(uptime+downtime)

Link to slides online gives a 404

Clicking on "The slides are available online." yields a 404 now. Was working last week.

chef-boneyard / devops-kungfu Goto Github PK

devops-kungfu's Introduction

Chef Style DevOps Kung fu

What is DevOps?

Practitioners of Chef Style DevOps

License

Based on reveal.js

devops-kungfu's People

Contributors

Stargazers

Watchers

Forkers

devops-kungfu's Issues

Describe the problem

Software Version

Replication Case

Stacktrace

Possible Solution

Recommend Projects

Recommend Topics

Recommend Org