4

I'm starting to examine Amazon OpsWorks and created a stack with a database layer and 2 custom layers. I put my cookbooks on a private git repository. I'm wondering why machines used in my scenario are so damn slow !? When booting the machines the first time it took around 15-30min until they are ready and even why I just start the task "update custom cookbooks" it takes 4(!!) minutes to fetch them from github. I already red about creating custom AMIs for reducing boot time but then I have to remove the opsworks-agent. Would I still be able to use the OpsWorks interface wehen removing the agent?

Do I miss something or is the process so slow for everyone? I'm using m1.small intances for testing purpose.

4
  • 1
    It's very slow for me too, I've asked a similar question on the AWS forums and got no response :( You can look through the logs for a run and see the breakdown by time, but there's nothing obvious consuming more time than it should. Otherwise OpsWorks is great! – thexacre Jul 5 '14 at 3:48
  • 1
    @thexacre yeah totally agree :/ – soupdiver Jul 8 '14 at 13:10
  • 1
    Yea it is extremely slow & very irritating at times. – Ram G Athreya Sep 30 '14 at 11:34
  • Probably depends on your target OS that you're trying to setup. I imagine a Windows-based system would take far longer to setup than something from the Linux realm. – Cyle Jan 5 '16 at 0:14
0

Because ruby is compiled during the running_setup to run the opsworks-agent if you are using an O.S. without ruby 2.0.0 by default. (i.e. the Amazon Linux AMI has ruby 2.0.0 built in, so is faster than ubuntu for provision).

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.