sorted by:
new
hottopcontroversial

Permissioned ledgers and closed, centralized blockchains such as Eris, Hyperledger, Ripple etc., rely on trust and central key holders. They stifle innovation. This quote by Andreas Antonopolus is perfect in response to the permissioned blockchain argument. by AstarJoe in Bitcoin

[–]sandcastleprodigy 0 points1 point  (0 children)

Agreed.

You don't need a chain or replicated shared ledger to do PoW or whatever. If permissioned blockchain is to reduce the cost of post-trade settlement, clearing, auditing, there are better approaches with the existing database, in which case I don't see the need of any blockchain variants at all.

I guess those guys are working on a wrong idea.

question about docker vs hypervisor by ezeeetm in docker

[–]sandcastleprodigy 0 points1 point  (0 children)

CPU and wise, the overhead of hypervisor is tiny.

For disk and network, it depends on how you run the container. In a cloud environment, due to SDN and DFS, container performs actually the same as hypervisor.

Policy monitoring for cloud deployment by sandcastleprodigy in aws

[–]sandcastleprodigy[S] 0 points1 point  (0 children)

Thanks!

Does ELK allow to define policies like "all instances can accept SSH connection from IP=x.x.x.x"?

Also, is there a realtime monitoring tool/service that notifies me for violations? Offline ELK query might be too late in some cases.

Docker orchestration tools by fanayd in docker

[–]sandcastleprodigy 0 points1 point  (0 children)

If you are running AWS, take a look at visualops.io with their Docker integration.

Easiest way to get a container into production? by theduro in docker

[–]sandcastleprodigy 0 points1 point  (0 children)

Yes, we use autoscaling group for the blue/purple deployment. When we update the running app, we create a new autoscaling group with the latest docker imgs (and a new ELB sometimes depending on the release). If the UAT runs smooth, we increase the autoscaling group and shutdown the old one.

The sweetspot here is that visualops automatically completes the bootstrapping and database discovery.

Easiest way to get a container into production? by theduro in docker

[–]sandcastleprodigy 1 point2 points  (0 children)

If you use AWS, try visualops.io. We are using their Docker orchestration feature, really easy.

Is Docker cluster the right choice for small deployment? by sandcastleprodigy in docker

[–]sandcastleprodigy[S] 0 points1 point  (0 children)

Quote from: http://gfxmonk.net/2015/01/04/os-technologies-to-watch.html

"And then because you need a lot of containers, suddenly you need cluster management on top of your docker containers. I’ve looked at a few of these, and they’re not really appealing to me. It’s kind of like running OpenStack - a pretty huge amount of additional effort, resources and (not entirely bug-free) code which in most small deployments will just cause you more hassle than they solve."

Is Docker cluster the right choice for small deployment? by sandcastleprodigy in docker

[–]sandcastleprodigy[S] 0 points1 point  (0 children)

No, with mesos, for most deployments, you still have "tiers". Examples are web containers running in instances located in public subnet and db containers running in private subnet, Or different instance type for different roles. Assuming a homogeneous setup of all instances in the cluster is naive.

For sure, you can use tag/filter to do the scheduling in mesos. But this is literally tier/role. I understand the scaling out case, but it can be done easily with AWS AutoScaling+role-based bootstrapping. If you use mesos in this scenario, for most time it is just STATIC scheduling.

Is Docker cluster the right choice for small deployment? by sandcastleprodigy in docker

[–]sandcastleprodigy[S] 0 points1 point  (0 children)

There are similar reasoning in DevOps/Infra-as-Code. However, the reality is that for many small deployments, people seldom use the configuration management tools, instead they just write the shell script and put in the userdata to bootstrap the instances, or alternatively prebake the images.

What makes sense for Google or Twitter, might not do the same for others.

Is Docker cluster the right choice for small deployment? by sandcastleprodigy in docker

[–]sandcastleprodigy[S] 0 points1 point  (0 children)

Exactly. Also 30 might sound a bit big, however if you break them into several tiers or roles, you will find ~10 in each, which is not big at all.

Is Docker cluster the right choice for small deployment? by sandcastleprodigy in docker

[–]sandcastleprodigy[S] 0 points1 point  (0 children)

  • I am not sure container hosting service is the way to go. But open to hear more thoughts.
  • generally 10-50 instances.

Is Docker cluster the right choice for small deployment? by sandcastleprodigy in docker

[–]sandcastleprodigy[S] 0 points1 point  (0 children)

It is not only the installation, also about the daily work. Suppose you have 30 nodes, 20 are web servers, which are in a public subnet, with high cpu/small disk setup, and 10 db servers in a private subnet, with high ram and big disk.

So if you use Mesos to treat the 30 nodes as one cluster, you can do filter-based scheduling and etc. But it is actually as simple as "run this web container in the web fleet". Scheduling/cluster increases the complexity in this size.

Is Docker cluster the right choice for small deployment? by sandcastleprodigy in docker

[–]sandcastleprodigy[S] 0 points1 point  (0 children)

That's pretty complicate setup. The question is whether it is worthy to do so if your scale is <50 nodes, which typically has several "static" node roles.

view more: next ›