6 ms·
We have ansible playbooks that we wrote leveraging some of the ansible-galaxy stuff, and they do the same thing either on-prems or in cloud. I would say we're p
by aprdm 5y ago
We have ansible playbooks that we wrote leveraging some of the ansible-galaxy stuff, and they do the same thing either on-prems or in cloud. I would say we're pretty cloud native, we follow best practices and deploying something to a cloud provider or internally is the same thing.
Our level of abstraction is containers, we don't use services that cloud providers sell, for example, Lambda, as they are very cloud provider specific. We prefer to use technologies like RabbitMQ which can be deployed on any cloud or on prems easily.
- goingindi 5y agoSo container first, deployed to vm or PaaS? Are you clustering the rabbit?
- aprdm 5y agoDeployed to VMs, internally vmware, outside whatever they have (e.g: EC2)
- westurner 5y agoAnsible & k8s: https://docs.ansible.com/ansible/latest/scenario_guides/kubernetes_scenarios/k8s_intro.html https://docs.ansible.com/ansible/latest/scenario_guides/kube... ansible-collections/kubernetes.core: https://github.com/ansible-collections/kubernetes.core https://github.com/ansible-collections/kubernetes.core geerlingguy/ansible-for-kubernetes book: https://github.com/geerlingguy/ansible-for-kubernetes https://github.com/geerlingguy/ansible-for-kubernetes openshift/openshift-ansible: https://github.com/openshift/openshift-ansible https://github.com/openshift/openshift-ansible
- westurner 5y agoOKD is the open source (RedHat, (IBM)) OpenShift, which wraps kubernetes ; sort of like AWX : https://github.com/openshift/okd https://github.com/openshift/okd > [OKD] Features: A fully automated distribution of Kubernetes on all major clouds and bare metal, OpenStack, and other virtualization providers; Single-node OpenShift 4 requires at least 16GB of RAM and 8 vCPU : https://www.redhat.com/en/blog/single-node-openshift-manufacturing-edge https://www.redhat.com/en/blog/single-node-openshift-manufac... > Single node OpenShift offers both control and worker node capabilities in a single server and provides users with a consistent experience across the sites where OpenShift is deployed, regardless of the size of the deployment. MicroShift requires 2Gb of RAM on e.g. an ARM64 Raspberry Pi 4 or similar SBC: https://microshift.io/docs/getting-started/ https://microshift.io/docs/getting-started/