In infrastructure-centric organizations, the IT operations team centrally manages infrastructure needs to efficiently utilize resources and streamline costs. To that end, IT defines policies and plans resources based on expected workload, budget, and general business requirements. Developers depend on IT for new machines to deploy applications and services, and again to dispose of or recycle them after use. From a developer’s point of view, this dependency slows down their development cycle.
But what happens when IT is delivered and consumed as a service, and when developers can deploy their applications on the organization’s infrastructure at will, at the click of a button?
IT as a Service with ElasticBox
In application-centric organizations, IT operations remove as much friction as possible. Infrastructure is provisioned from the top down, based on the resources needed to serve the application.
IT as a Service empowers both the IT and the development teams. Empowers IT because they no longer focus on low-level constraints around infrastructure, but on high-value activities around applications. Empowers developers because they can shape their ideas into reality in production faster, focus 100% on writing code rather than tinker with the underlying infrastructure.
Developers now have access to infrastructure on demand and consume resources without process bottlenecks. At the same time, organizations still need to use resources efficiently and stay within their allotted resource plan and budget. That is why, developers, under IT operations supervision, need to keep the full lease management process under control, from provisioning to disposing infrastructure.
Consume mindfully with the Instance Scheduler
ElasticBox already made it transparent and simple for IT operations and developers to provision, deploy, and orchestrate applications on demand.
We enhance that experience by introducing the ElasticBox Instance Scheduler. The scheduler lets you time disposal of infrastructure automatically when you know you only need it for a select time range.
You can set custom shutdown and termination policies in ElasticBox when launching an instance. Specify, for example, that an instance should terminate after 1 hour, or on a given date and time. This kind of scheduling is great if you want to test a new deployment configuration, or want to spin up a test or development environment for a limited timespan.
Along with the ability for the IT persona to set budgets and quotas, the scheduler gives developers added flexibility to ensure they only use what IT has planned.
The option to schedule instances is available at deploy time in the deployment profile dialog in ElasticBox. Once launched, you can create or edit its schedule from the instances page as well. Get more details from our documentation here.