Greg Horie wrote:Hi Ian
To clarify, 'running your own private cloud' means a private OpenStack instance. Its a lot to manage and challenging to do it well.
Greg Horie wrote:Hi Pini, Jamie, Michelle
Do you see a benefit in running a private cloud for VMs (e.g. openstack) when your infrastructure can run on containers? I know there are benefits, but do these outweigh all the operational costs of running your own private cloud for a production operations?
Amandeep Singh Ghai wrote:Hello Ian,
I was too quick to post that question without much details. I essentially meant:
* Data Dependencies: Usually with sharing of data per Web-Service / FTP etc...
* Library Dependencies: We also have framework supporting several applications, that use common libraries & those are also updated quite often.
What kind of challenges are presented under such situations?
Palak Mathur wrote:
Ian Miell wrote:
This is why our book contains a lot of material considered 'impure' Docker - ie not microservices, monolithic and not highly orchestrated 'data centre as an operating system' type work.
Docker helped us turn our monolithic application into a single unit which could be easily shipped for testing or support or dev purposes. We wrote our own simple automation tool to help achieve this - ShutIt
I think we are also some impure "Docker" work. Some of our stuff is not microservices at all. Docker is really interesting in the opportunities it seem to provide for all sorts of applications.
Will Myers wrote:Hi,
How does Docker In Practice differ from Docker In Action?
Does it delve deeper into the topics and maybe skip some that are less important?
As a beginner, would Docker In Practice be a good starting point to learn the technology?
paul nisset wrote:
Thank you for your responses.
I was thinking of using it more in the way Palak mentioned
You can set docker to configure the container the way you want and carry the same container across platforms - your in-premises network to an EC2 instance.
seems like an interesting use for testing a service .
simulating the interaction between 20 different servers
If I were to this would I create/copy a new Docker instance for each server that would be calling the service?
Luca Botti wrote:Hi all,
I am just asking because Docker, while simple at the start, requires a complete new mindset related to deployment. And, to me, it looks like to be "production ready" it needs a complete devops infrastructure to be effective.
While experimenting from the command line is quite simple, things can get out of control fast, so the complete "assemble-deploy-manage" shall be in place. Not only Kubernetes or Swarm, but also on the Dev side (whatever you use).
Just my thinking.