Agreed. We are a cloud based org and an ASP. We stand up the hosts to run our apps. Power downs for any nonprod not an option for us.
An earlier answer on setting up dependencies seems to me the way to go. Sent from my iPhone > On Jun 16, 2016, at 8:49 AM, Matt Shields <m...@shields.tv> wrote: > > If this were a datacenter where I have purchased my hardware and have a fixed > monthly budget for datacenter space and power, then the only cost to me is > the wear of leaving servers powered on. Most datacenter have fixed billing > for the circuits you have installed, not the actual power consumed. And some > would say that it makes more sense to leave the machines powered on because > it's less wear than powering on/off every day. > > In the cloud, we pay by the hour for every resource left on. Our cost is > approximately 2/3 of what it could be because we have people shutdown > resources that are not in use. > >> On Thu, Jun 16, 2016 at 8:45 AM, Matt Shields <m...@shields.tv> wrote: >> They are AWS instances for Dev and QA, there's no logical reason to leave >> them powered on when they're not in use. The dev/qa guys can log into AWS >> and power them on and off as needed. >> >>> On Thu, Jun 16, 2016 at 8:20 AM, Felix Cruz <felix1...@gmail.com> wrote: >>> Hi >>> >>> I don't disagree with that. I am not our monitoring engineer I am with >>> Ops. So a technical solution I can't provide. Process wise it makes no >>> sense to power off machines especially if they require monitoring. How >>> would you automate the handling of a random power off event with unknown >>> time interval, or distinguish it from a genuine unhandled event that >>> requires an action? > > _______________________________________________ > icinga-users mailing list > icinga-users@lists.icinga.org > https://lists.icinga.org/mailman/listinfo/icinga-users
_______________________________________________ icinga-users mailing list icinga-users@lists.icinga.org https://lists.icinga.org/mailman/listinfo/icinga-users
