11–20 of 140 posts
Spinnaker is an amazing tool. Really makes it easy to confidently deploy applications via immutable infrastructure.
Can some one explain to me what immutable means in terms of "infrastructure" ?
Spinnaker is an amazing tool. Really makes it easy to confidently deploy applications via immutable infrastructure.
Can some one explain to me what immutable means in terms of "infrastructure" ?
The image the EC2 instance is started from is immutable while it is running. Of course the image gets updated regularly by devops with security fixes, but the running production instance(s) is/are never changed on the fly. Instead it is completely redeployed.
Spinnaker is an amazing tool. Really makes it easy to confidently deploy applications via immutable infrastructure.
Can some one explain to me what immutable means in terms of "infrastructure" ?
Spinnaker is an amazing tool. Really makes it easy to confidently deploy applications via immutable infrastructure.
Can some one explain to me what immutable means in terms of "infrastructure" ?
Would you fix a software bug by editing the code on a running server and tell yourself that you will add it to the repository later? Of course not. You would end up with a running instance of the code that is impossible to replicate.
Immutable infrastructure applies that same idea to running services.
Earlier quoted context omitted.
Can some one explain to me what immutable means in terms of "infrastructure" ?
Simplified: Instead of modifying a deployment by uninstalling the old software, updating the config files and installing a new version, you create a new virtual machine image with all you need and deploy instances of that. Even if you just want to change a setting in a file you deploy new virtual machines. There are variations of this such as using Docker.
Spinnaker is an amazing tool. Really makes it easy to confidently deploy applications via immutable infrastructure.
I think that the future of deployments means that it is closely integrated with your source code management. Every new push builds a container that can go through the following steps:
1. Deployment (server with only test traffic)
2. Post-deploy test (smoke test)
3. Canary (part of the traffic)
4. Live / multiregion deploy
5. Manual overrides http://techblog.netflix.com/2015/11/global-continuous-delive... "Spinnaker also provides cluster management capabilities and provides deep visibility into an application’s cloud footprint. Via Spinnaker’s application view, you can resize, delete, disable, and even manually deploy new server groups using strategies like Blue-Green (or Red-Black as we call it at Netflix). You can create, edit, and destroy load balancers as well as security groups."
Also see https://gitlab.com/gitlab-org/gitlab-ce/issues/3286
Spinnaker is an amazing tool. Really makes it easy to confidently deploy applications via immutable infrastructure.
Immutable infrastructure is the future and it seems that even Netflix is planning to use containers for that: "Containers provide an interesting potential solution to the last two challenges and we are exploring how containers can help improve our current build, bake, and deploy experience." I think that the future of deployments means that it is closely integrated with your source code management. Every new push bui…
Spinnaker is an amazing tool. Really makes it easy to confidently deploy applications via immutable infrastructure.
Immutable infrastructure is the future and it seems that even Netflix is planning to use containers for that: "Containers provide an interesting potential solution to the last two challenges and we are exploring how containers can help improve our current build, bake, and deploy experience." I think that the future of deployments means that it is closely integrated with your source code management. Every new push bui…
Are there any downsides to immutable infrastructure?
Earlier quoted context omitted.
Immutable infrastructure is the future and it seems that even Netflix is planning to use containers for that: "Containers provide an interesting potential solution to the last two challenges and we are exploring how containers can help improve our current build, bake, and deploy experience." I think that the future of deployments means that it is closely integrated with your source code management. Every new push bui…
> Immutable infrastructure is the future Are there any downsides to immutable infrastructure?
Spinnaker is an amazing tool. Really makes it easy to confidently deploy applications via immutable infrastructure.
Can some one explain to me what immutable means in terms of "infrastructure" ?
If it works for me it works for everyone.
You never patch or upgrade immutable infrastructure. You just replace what you've got with a new VM or container. Containers being preferred because they can be started & stopped near instantaneously and there's nothing like a virtual BIOS that could have different configurations like with VMs.
You don't stand up a VM or container then "log in to configure it". Once the VM is "up" that's it. You're done. At that point you just need to point your load balancers/DNS at the new stuff then take down the old stuff.
One interesting aspect of immutable infrastructure such as this is that it is completely incompatible with loads of existing security policies and what would have been considered "best practices" just a few years ago. For example, you might have a security policy that states that everything must be scanned within 30 days for malware/out-of-date packages/whatever. Yet with immutable infrastructure your hosts or containers may only be up for a few days before being replaced!
So when your security team freaks out because none of your hosts/containers are showing up in their systems you'll have a lot of explaining to do =D
"We need to scan your hosts so we can ensure that you're installing security patches."
"We don't do that."
"You don't install security patches?!?"
"Yeah, well, you see..."
Trust me when I say that trying to explain how it all works and why it's more secure than old school deployments is not easy!