This week's book giveaways are in the Jython/Python and Object-Oriented programming forums.
We're giving away four copies each of Machine Learning for Business: Using Amazon SageMaker and Jupyter and Object Design Style Guide and have the authors on-line!
See this thread and this one for details.
Win a copy of Machine Learning for Business: Using Amazon SageMaker and JupyterE this week in the Jython/Python forum
or Object Design Style Guide in the Object-Oriented programming forum!

Greg Horie

Greenhorn
+ Follow
since Jun 21, 2010
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Greg Horie

@Stephen
OpenShift 4 now defaults to CRI-O - https://www.redhat.com/en/blog/red-hat-openshift-container-platform-4-now-defaults-cri-o-underlying-container-engine.


@Tim
Yeah, I feel the same. Docker still fits the need for my enterprise services. That said, I understand it is not the best solution for some container use cases. That led me to think of this other topic - https://coderanch.com/t/726545/engineering/Docker-Action-Docker-LXC-LXD. Unfortunately, no one seems interested in this one (yet).
2 weeks ago
I encounter a fair number of folks that express some animosity towards Docker for managing containers. These folks typically like the raw LXC/LXD approach as an alternative. I think these are all reasonable solutions, but it depends on the use case. What use cases (if any) do you think are best left for the LXC/LXD approach?
2 weeks ago
I'm wondering if you have any experience with other container runtimes - e.g. CRI-O, containerd. I continue to stick close to Docker, but I'm wondering if I should be exploring these other options.
2 weeks ago
Thanks for the response Ian! All this feedback has been very helpful.

Cheers,
Greg
1 month ago
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.

1 month ago
Hi Michelle

Thanks for your comments!

We do have some data restrictions, but another consideration is latency back into our enterprise and service networks. We need to ensure low latency in some very specific use cases.

Another concern I have is cognitive load. If our architecture is hybrid or some other interesting combination of cloud / containers / public / private, then its more brain-power spent on technical requirements and less time focused on customer needs. Ideally, I wish we had only one infrastructure paradigm to manage, but it seems we currently have to embrace many.  

1 month ago
Thanks for the response Pini.

Yes, this consistent with my experience as well. OpenStack is challenging. Public cloud Kubernetes is a much easier path (assuming public cloud and containers work for your use cases).

I haven't tried OpenShift or GiantSwarm. I should probably read up more on these solutions because some of our upcoming container-based solutions will not be permitted in a public cloud.

Cheers,
Greg
1 month ago
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?

Cheers,
Greg
1 month ago
Those are good points. Public cloud does have its risks. Some can be mitigated through design choices, but no one can catch them all.

I'm hoping that Kubernetes / containers will become our main infrastructure choice for solutions that we don't want to host in a public cloud. Containers aren't going to solve all use cases, but I think they can go a long way and I'm hoping over time they will simplify our infrastructure. From a hobbyist perspective, its fun to learn about all the things. From an enterprise service perspective, simpler would be nice for faster time-to-market and ease of management.

1 month ago
Hi Michelle & Pini

It sounds like the book has some patterns that I'll be able to employ. I'm certainly not interested in change for change's sake. My concern is keeping ahead of degrading hardware and adopting migration patterns that provide a smooth transition for our customer services.

Thanks for your feedback!

Cheers,
Greg
1 month ago
Hey Tim

Oh you're right about OpenStack losing its luster. We're currently using it for some of our services. It adds a lot overhead and I don't see the value. For our use cases I'd rather go with public cloud options or Kubernetes.

I'm also curious about moving things onto a set of RPis! Its on my list, but you know ... time.  :-)

Cheers,
Greg

1 month ago
Hi Pini, Jamie, and Michelle

My production operations is spread over many generations of tech - from legacy, bare-metal to cloud VMs / containers. Are there any patterns from the cloud native world that can/should be used on the legacy side or is it better to leave the legacy to follow its old deployment model (i.e. pets that require a lots of hands-on love) until the boxes disintegrate?

Cheers,
Greg
1 month ago
Thanks for the response Justin.

Yeah, I hope writing software becomes easier as well. As someone who straddles building/maintaining infrastructure as well as writing the occasional code, I can't say its any easier at this point in time.  :-)

Kubernetes and containers do offer a compelling set of abstractions that (hopefully) will make life easier in the long run.

Cheers,
Greg
1 month ago
Okay, I'm going to ask you to pull our your crystal balls.  :-)

If you look into the future, do you see containers ruling the enterprise? Will there still a place for bare-metal in most enterprises?

Also, where do you see FaaS fitting into this future?

Cheers,
Greg

1 month ago
In my case we are using Prometheus and we also manage services that are published by 3rd party providers and these providers are promoting the use of Helm. I see the benefits in the release and rollback functionality, so for this reason alone we'll continue down this path.

I hadn't considered publishing our own charts, but I can see where this may be useful for my team. I'll have to check-out the section of your book on Helm.

Cheers,
Greg
1 month ago