This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
sig:sysadmin:projects:project18 [2016/06/16 22:39] clee231 2016 Updates |
sig:sysadmin:projects:project18 [2021/05/02 21:36] (current) |
||
---|---|---|---|
Line 44: | Line 44: | ||
====== Progress ====== | ====== Progress ====== | ||
- | We have chosen Docker as the method of containment for such applications and CoreOS as a means of holding and scaling these containers. Typically, a user would write a systemd unit file that would typically download a docker container, name the container, and deploy it across the cluster, lettings CoreOS balance the load. While this granularity is fine for a select few, it will be too much work for someone that wants to quickly deploy their application. | + | We will be experimenting with both docker and rkt container engines. The current cluster will most likely be reinstalled. We have briefly discussed the project over the weeks via listserv and SIG meetings. I think we will be settling on a master node to orchestrate the cluster. The master node will also host a master etcd server and a kubernetes-head server. The remaining nodes will be worker nodes. |
+ | |||
+ | ===== Roadmap ===== | ||
+ | |||
+ | - Create cloud-config base for master and worker nodes. | ||
+ | * Note to account for: | ||
+ | * Bonded interface | ||
+ | * Internal DHCP server bonded interface | ||
+ | * external traffic interface | ||
+ | * Starting master etcd instance on master node for other machines to sync off of. | ||
+ | * Starting fleetctl | ||
+ | - Install Kubernetes | ||
+ | - Install Test load balancers | ||
+ | - Install whatever else... | ||
===== Orchestration/Deployment tools for CoreOS ===== | ===== Orchestration/Deployment tools for CoreOS ===== |