3 ms·
This! I think #1 and #2 should be the same people. with PaaS I don't see any need for "operators". If an engineer can't launch a new service with all the requ
by avitzurel 10y ago
This!
I think #1 and #2 should be the same people. with PaaS I don't see any need for "operators".
If an engineer can't launch a new service with all the requirements EASILY, you're doing something wrong
You're == all of us, myself included.
- jacques_chester 10y ago> with PaaS I don't see any need for "operators". Yes and no. What we're finding is that you need far fewer operators. But you still need someone to keep an eye on things and run 'bosh deploy' to upgrade the cluster or add a new service. The latter could be automated, but it's one of those things people like to do under supervision. At Pivotal we run Pivotal Web Services (PWS) -- a version of Cloud Foundry which is usually less than a week behind the current release -- with three shifts of 3-10 people each. Two to five pairs, is how we think of it. PWS has thousands of VMs and tens of thousands of applications running. Pre-CF, pre-BOSH, an installation of this magnitude would need hundreds of sysadmins to stop it from immediately bursting into pretty but expensive flames. But in general, you're right. The contract with engineers is "tell me what you want and I'll give it to you". Cloud Foundry does that well.