Showing posts with label DevOps. Show all posts
Showing posts with label DevOps. Show all posts

Tuesday, June 23, 2015

Booyah: Continuously Deploying our Azure services

Awesome! So I'm breaking up a monolithic application into cloud services which I'll host on the Azure platform. I had it up, running, and publishable from Visual Studio, with all the correct configs for the right environments.

Then I came across this blogpost: https://azure.microsoft.com/en-gb/documentation/articles/cloud-services-continuous-delivery-use-vso/ YES you should read it and see the awesomeness.

So now I'm continuously deploying my services on checkin to Azure - here's the proof:


Awesome. Do read the post - there are some little tips and tricks in there ( for instance, how to make sure the config transforms properly ). But if you have all the publish profiles set up correctly before, AND you're build server is up to date ( with build targets and things ), it'll be a breeze.

This is from the mentioned blog - this button gets you 90% of the way for you build configuration:


Tuesday, July 30, 2013

PuppetConf 2012 video collection

Probably hugely outdated by now, but still very interesting to me is this page on the Puppet website listing all the talks of PuppetConf2012.

One talk the really caught my attention was the talk by Gene Kim about DevOps was really interesting. Sure, this talk doesn't necessarily have anything to do with puppet and is more about DevOps, but I liked it so much because it talks about some of the stuff I see going on in my company. One of the points that he briefly mentions and that Puppet allows you to do, is include the machine configuration into the source code. Oh yes - so if Dev includes a puppet file in the source code, Ops can just take that, spin it up and get the app running.

We do have something like that in place, where we have a scripted deployment of the application that is checked into source control, but it won't do it 'from scratch'.



This guy has written award winning books - check them out here.

Saturday, July 20, 2013

Cool stuff to look out for: Puppet and Vagrant

A while ago my ex-colleague sent me a blog about a guy who started a company and started out by setting up his OTAP environment using Puppet and Vagrant. Let's quickly look at what these projects are:

Puppet

"Puppet Enterprise is IT automation software that gives system administrators the power to easily automate repetitive tasks, quickly deploy critical applications, and proactively manage infrastructure, on-premises or in the cloud." - https://puppetlabs.com/puppet/puppet-enterprise/

So it's a piece of software that lets you control 'the state of resources' on your 'nodes', which will probably VMs. You can see in the video's that a puppet master ( a box that controls the puppet boxes ) uses a configuration file to set the box's network config ( IP stuff ) and for instance the installed mods ( LAMP, node and/or other db engines).

Vagrant

"Vagrant provides easy to configure, reproducible, and portable work environments built on top of industry-standard technology and controlled by a single consistent workflow to help maximize the productivity and flexibility of you and your team. To achieve its magic, Vagrant stands on the shoulders of giants. Machines are provisioned on top of VirtualBox, VMware, AWS, or any other provider. Then, industry-standard provisioning tools such as shell scripts, Chef, or Puppet, can be used to automatically install and configure software on the machine." - http://docs.vagrantup.com/v2/why-vagrant/index.html

The way these things come together is that you can script the creation of one ( or a WHOLE lot ) of VMs and then configure them using puppet to either take on a certain role ( test your load balancing for instance ) or make them perform a certain task.

Really awesome stuff if you ask me. Things like that should be possible with Windows Azure I suppose, so I need to get up to speed with that stuff too.




Thursday, May 16, 2013

Interesting Channel 9 talk: Building an Engineering Organization for Continuous Delivery

Here's a nice talk from Brian Harry about DevOps practices and how he and his TFS team moved from a 'waterfallian' model to a more agile model. I watched it and I liked it. It's described as:

Brian Harry shares behind-the-scenes information on how Team Foundation Service is developed and announces exciting additions in his ALM Summit keynote. As of now, Team Foundation Service provides a distributed version control offering with Git repos, and Visual Studio offers full Git integration with Visual Studio 2012 Update (currently available as a CTP release), including the option to use 3rd-party hosts. In a future release, Team Foundation Server will also support Git repos. Developers who want to use distributed version control systems can now get started quickly from within Visual Studio. This expansion of ALM options makes it easier for teams to adopt tools that are best suited to their specific needs.

See it here or use the video below: