fleet

Auto Scaling 就不能綁個 Lambda 嗎...

看到 AWS 宣佈 Amazon EC2 的 auto scaling 有新花樣：「New – Attribute-Based Instance Type Selection for EC2 Auto Scaling and EC2 Fleet」。

你都有 Lambda 了，就不能整合 Lambda 每分鐘跑一次，讓使用者直接用個 turing complete 的方式自己設計要的 policy 嗎... 會用到 auto scaling 的使用者不會在意 Lambda 的那幾毛錢的。

這樣做對 OKR 是比較好沒錯啦，但用的人已經懶的看了...

AWS 推出 EC2 Fleet：直接混搭標準 EC2、Spot、RI 的計算

AWS 將本來 EC2 的 Spot Fleet 加上了 EC2 Fleet，計算的公式從本來只有 Spot Instace，變成把標準 EC2 Instance 與 RI 的計算全部都納進來：「EC2 Fleet – Manage Thousands of On-Demand and Spot Instances with One Request」。

Today we are extending and generalizing the set-it-and-forget-it model that we pioneered in Spot Fleet with EC2 Fleet, a new building block that gives you the ability to create fleets that are composed of a combination of EC2 On-Demand, Reserved, and Spot Instances with a single API call.

不過目前有些服務還沒整，主要是跟 auto scaling 有關的部份，這部份應該是一次上一大包：

We plan to connect EC2 Fleet and EC2 Auto Scaling groups. This will let you create a single fleet that mixed instance types and Spot, Reserved and On-Demand, while also taking advantage of EC2 Auto Scaling features such as health checks and lifecycle hooks. This integration will also bring EC2 Fleet functionality to services such as Amazon ECS, Amazon EKS, and AWS Batch that build on and make use of EC2 Auto Scaling for fleet management.

整完以後對於要省成本就更簡單了...

Amazon EMR 支援 Instance Fleet 了

所以 Amazon EMR 在 Spot Instance 競價的時候可以使用 Instance Fleet 了：「New – Amazon EMR Instance Fleets」。

雖然機器比較小台而導致數量多一些的時候會有 overhead (通常)，但更容易保持穩定的價錢...

填補 Caltrain 營運空缺的 Fleet

去年年底參加 Spark Summit 時有用 Caltrain 當作交通工具回飯店，好像是搭到末班車... (或者說是接近末班車？有點忘了...)

Fleet 的服務則是填補 Caltrain 減班或是休息的時候，用小型車在 Caltrain 的幾個大站提供服務：

Ride with friends, or meet other cool people on the way; we drive in a car, van, or shuttle seating 5 to 15 people.

Our shuttles run between 8 PM and 5 AM everyday, with 5 southbound departures, and 5 northbound departures.

另外主打比 Uber 便宜許多：

We are also ~2-4X cheaper than Uber and other ridesharing alternatives.

還蠻有趣的嘗試，不知道成效如何...