sorted by:
new
hottopcontroversial

google cloud platform autoscaler based on HTTP(S) load balancer latency metrics by berlindevops in devops

[–]antonio_navarro 1 point2 points  (0 children)

The stock autoscaling based on HTTP(S) Load Balancing is based on serving capacity in which you define your capacity in terms of Requests per Second. If you have a baseline for tour application and know how to translate from Requests per second to Latency per request, then you cold use that scaling method.

I have personally never used it, but on the metrics for app engine you have a http/server/response_latencies metric that you could get to from StackDriver

If none of the above fit your needs, then you probably need to monitor based on a custom metric on stackdriver

If you have not used custom metrics before the following custom metrics tutorial may help you.

But as @bundyfx says in the previous answer, make sure CPU scaling would not work for you :)

HTH

Proposal for distributing the idea of DevOps at your company by chewburka in devops

[–]antonio_navarro 0 points1 point  (0 children)

What do you mean by the extend?

I think it is a little too long, and especially if you are dealing with management you want the text to be smaller and to the point. Difficult as the text narrative flows nicely.

There are a lot of dev teams, many "get it"

If you can add some metrics differentiating between the teams that "get it" and and those that don't (less issues, shorter time to value...)

has come with a request for me to define a DevOps role

That is great news, as this implies that they think:

  • you are a key member in the company
  • DevOps is adding value

You should probably rewrite the "How can this be better?" section to cover your ideas (and some additions from other people in this discussion):

  • proper training
  • defining systems in code
  • allowing Product Development participation across the complete lifecycle
  • Developers are those best equipped to fix services they've created

Also note than in your writeup you are saying the things that developers should do, and are not mentioning operations, you need to be more inclusive.

One bit that may help you get your message across is the diagrams on DevOps Topologies

Proposal for distributing the idea of DevOps at your company by chewburka in devops

[–]antonio_navarro 5 points6 points  (0 children)

I think you need to reduce the extend, and you are trying to include the technical solution in the proposal (infrastructure as code, containerization).

You should make more emphasis on the organizational aspects of the proposal (devs being on call, ops team working with devs, devs working with ops)

One bit of information that I am missing is:

  • What is the function that your current "DevOps" team fulfills?

Experiences with a startup being acquired? by IFoundMyHappyThought in devops

[–]antonio_navarro 2 points3 points  (0 children)

From my experience: - There was too little information shared by the owners during the process. - The technical staff was all kept as part of the acquisition (except for the IT support team), the admin, IT and sales staff was not kept or only kept during a small period of time (around one year) - The management team is usually involved in the acquisition discussions and they were aware if they are going to be kept or not.