kt9

You can use your own build servers with distelli and any images and layers pulled down during one build will be cached and available on subsequent builds. So even though distelli is a hosted service you don't have to run builds on our shared build machines. You can fire up your own build servers and connect them to our service and you'll get all the benefits of a dedicated build server including caching.

https://www.distelli.com/docs/kb/using-your-own-build-server

Thanks for letting us know. btw we also offer our service as an on-prem solution so ping me and we can get you setup if you prefer that.

We have our own software to create k8s clusters in AWS using weave for networking. We looked at kube-up etc but our customers wanted functionality that didn't force them to create a brand new VPC created but instead just launch multiple clusters in an existing VPC.

FYI we are going to release our kube laucher as open source in the next few months. If you sign up for our mailing list or email me at rsingh@distelli.com (or follow us on twitter / fb) i'll notify you when thats available if you're interested.

Yes, we can kick off a kubernetes deployment based on the pipeline rules you specify from any CI server that can make an API call to our service.

So you can use Jenkins or Gitlab CI or any other CI you like and when that system reports a CI pass we can kick off the deploy to your k8s cluster.

They are static pages served from the same webserver but there was a bug where we were erroneously hitting a DynamoDB table.

Hi everyone,

We found that the site was slow because we were getting throttled by a table in DynamoDB which explains why kubectl scale wasn't helping as much as we had hoped. We were adding capacity, just not in the right place.

We've added read capacity to our table and things are faster now.

Distelli offers a visual dashboard around Kubernetes that makes working with Kubernetes extremely simple. It allows users to set rule-based visual pipelines that make automatic updates to one's Kubernetes cluster while also allowing one to work with the Kubernetes YAML system.

By looking at the distelli UI one can easily see who did what build or deploy and when. One can even restrict certain actions from certain users by placing users in permission groups.

Additionally, distelli provides a dashboard to provision and manage clusters on multiple clouds providers.

Finally, while distelli offers a build system for CI, it also works nicely with other CI systems so one can use Drone and Distelli together.

edit: grammar

Hi,

AWS doesn't support kubernetes natively. We allow you to either launch a new kubernetes cluster on AWS by launching new VMs and installing kubernetes, weave and etcd or we allow you to sync an existing kubernetes cluster running on AWS by providing the k8s master endpoint.

We don't currently support ECS clusters but that is on our roadmap.

hehe. Yup we just scaled up.

Sorry we're scaling up under the load from HN traffic. Email me at rsingh@distelli.com and I'll be happy to help you with pricing or any other questions you might have.

We (distelli) do provide our own CI system but you don't have to use ours. You can use your own CI system and kick off the pipeline from that.

Some of our customers use Jenkins while others use one of the many hosted CI systems.

We still support the VM, bare metal use cases. We've just created a new landing page around k8s because its our latest offering and its on our list to add additional pages around our existing VM use cases.

There are many way to do this but we (distelli) recommend the following:

1. Run automated tests during container build (maybe in the AfterBuildSuccess step)

2. Have a single image that goes to both staging and production. Pass in environment variables or configs to operate the image differently in staging or prod

3. Don't include test dependencies in the image so the image is smaller. So if you're running tests etc don't add the tests and dependencies in the Dockerfile. Instead have your CI system run the tests.

I'm the founder at Distelli. I'm happy to answer any questions.

Hi you can build iOS applications using Distelli and your own build servers - https://www.distelli.com/docs/kb/using-your-own-build-server

disclaimer: I'm the founder at distelli

Thanks for the great feedback charlie! Based on your feedback we've added 2 new features to distelli this week.

You can now create and manage Kubernetes services in distelli and also use your own K8S deployment yaml.

Checkout the new features at https://www.distelli.com and thanks for the feedback and for helping us build a better product.

Thanks for checking it out. If you have questions you can contact us at support@distelli.com or ping me directly at rsingh@distelli.com.

Happy to help and look forward to your feedback.

Wercker will build your docker images but deployments from wercker to k8s require kubectl, which makes it hard to setup pipelines that deploy from dev -> test automatically and then promote to prod manually once test is working fine.

In the scenario above dev and test are assumed to be different namespaces on same or different clusters.

Finally we have a complete cluster management dashboard and UI so you can launch new clusters and administer existing ones right in the UI.

I'm the Founder at Distelli and we've been helping our customers deploy to VMs for almost a year.

Now we've gotten several requests from folks asking us if we can build pipelines to their Kubernetes Clusters and we're excited to share what we've built.

We're a small group of engineers and we value honest feedback so tell us what you think.

I'm the founder at Distelli and I just want to clarify that the Distelli agent doesn't typically live inside the container though it can. Its used to orchestrate the container lifecycle on the VM itself.

However if you're building Docker containers and deploying them we recommend using Kubernetes which is something that Distelli supports out of the box now - https://www.distelli.com

The reason the Java HashMap get() is not O(1) is because of separate chaining. The HashMap handles hash collisions by adding all colliding entries to a Linked List and lookups have to hash to the correct bucket and then iterate over the linked list in that bucket. So the complexity of a get() is O(1)+O(k) where k is the number of items in the LinkedList.

https://en.wikipedia.org/wiki/Hash_table#Separate_chaining

This is actually a great point.

If I did any UI pieces it would probably be in React talking back to an API handled by the core server.

Check out Distelli - https://www.distelli.com

Disclaimer: I'm the founder

Domain registrars that engaged in holding domains hostage and increasing prices would probably eventually go out of business.

Even if that ended up not being the case, we'd have to fix how domains are transferred between registrars - same as how telephone numbers can be transferred between telcos but you can't sell your telephone number to someone.

Coase theorem applies if there are a) zero or sufficiently low transaction costs and b) if parties are able to bargain.

If domains have to be returned back to the registrar b) doesn't apply. Auctions ensure that a) doesn't apply either.

Furthermore, adding a 7 day waiting period before returned domains become available will further ensure that parties cannot trade domains between each other but must purchase from the registrar which makes owning a domain and squatting on it for purposes of selling it pointless.

The best way to eliminate domain squatting is to make domains non-transferrable. If you own a domain you shouldn't be able to transfer it to anyone. The only way to "transfer" a domain should be to return it to the domain registry where it may be purchased by any interested party at market price determined by auction.

However this probably isn't going to change.

Thanks @doublerebel. For those interested Distelli is at https://www.distelli.com

Disclaimer: I'm the founder at @distelli

yes we did consider Golang but Brian' familiarity with Lua was a major factor in the decision. Most importantly however, we foster a culture of ownership and it was Brian's decision to own and he owned it and it was the right decision.

Shipping it as a single download with zero dependencies meant that we would not have to worry in the future about what else was installed on the machine and the versions of system packaged the customers were running.