Hacker News new | comments | show | ask | jobs | submit login
Show HN: My first book: Orchestrating Docker (amazon.com)
32 points by shrikrishna 721 days ago | hide | past | web | 7 comments | favorite



My first though on reading the title was "How can you write a book about docker and orchestration now? The tech is too immature and evolving too quickly." From the table of contents, it looks like the book doesn't actually focus on orchestration.

  1: UNBOXING DOCKER
  Installing Docker
  OpenStack
  Inception: Build Docker in Docker
  Verifying Installation
  Useful tips
  Summary

  2: DOCKER CLI AND DOCKERFILE
  Docker terminologies
  Docker commands
  Running your own project
  Dockerfile
  Docker workflow - pull-use-modify-commit-push
  Automated Builds
  Summary

  3: CONFIGURING DOCKER CONTAINERS
  Constraining resources
  Managing data in containers with volumes
  Configuring Docker to use a different storage driver
  Configuring Docker's network settings
  Linking containers
  Summary

  4: AUTOMATION AND BEST PRACTICES
  Docker remote API
  Injecting processes into containers with the Docker execute command
  Service discovery
  Security
  Summary

  5: FRIENDS OF DOCKER
  Using Docker with Chef and Puppet
  Setting up an apt-cacher
  Setting up your own mini-Heroku
  Setting up a highly available service
  Summary
I found the table of contents at https://www.packtpub.com/virtualization-and-cloud/orchestrat...


That is true. This is more of a book about Docker than about orchestration. The naming is unfortunate, and something that I did not have control on.


Okay, I understand now. Congratulations on being published! I'm sure it was a lot of hard work to write this.


Serious question .. How does one define orchestration? Openstack heat is an example of an orchestration system as is fig. But I don't think I can define the term clearly.


It's not a simple answer, but http://en.wikipedia.org/wiki/Orchestration_(computing) characterizes it as

* Composing of architecture, tools and processes used by humans to deliver a defined Service.

* Stitching of software and hardware components together to deliver a defined Service.

* Connecting and Automating of work flows when applicable to deliver a defined Service.


Congrats on publishing.

Since this is your first book, and you have no immediately obvious prior published authority on the matter of Docker, I recommend you improve your Amazon author profile.

Currently I see the book and think, "this looks good!" But then I ask, "wait who is this guy, and why does he know so much about Docker?" Your author profile should answer that question, but right now it's just a brief picture of your personality. Sell yourself. Explain why you are the best person to teach me about Docker.

Always establish your authority. :)


Thanks for that tip! Will do.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: