Provisioning New Environments with a Private Cloud





The interactive transcript could not be loaded.



Rating is available when the video has been rented.
This feature is not available right now. Please try again later.
Published on Oct 15, 2012


Peter Bews from Rogers Communications discusses how private clouds have enabled fit-for-purpose environment provisioning.

Rogers is an integrated full-service telecommunications company, so we do wireless services, cell phones, that kind of thing.

I spent time interviewing with all of the people that would—sort of my peer group, understanding what was working well, what wasn't working well. What I heard a lot of was inability for infrastructure to provision new environments when they needed them.

We also heard lack of flexibility. Some of the process to obtain infrastructure was longer than people would have liked and probably more cumbersome than they would like as well. So it forced us to then look at new and different ways of obtaining these new environments, these capabilities.

I think the other big area that we heard a lot about was how our non-production environments, how we provisioned them, how many of them we had, utilization of them, and whether or not they were fit for purpose across the way we wanted to use them.

So our solution that we decided to go with was an internal private cloud. What we decided to implement was a dedicated cloud per workload type, so we're actually building five clouds. So we're building a cloud around our production environment, obviously, and our disaster recovery environment, but we're also building dedicated clouds for development and testing as well as for performance testing.

The reason for the segregated environments is around the ability to provide an additional level of manageability to the end user in our non-production environments. The fifth cloud is really the cloud for us to be able to develop our cloud solution. So we needed a place to test the cloud services themselves, and that's our lab.

IBM's role in our journey is really—they've played the leadership role in a lot of what we're doing, so they're the architects behind the technical solution.


When autoplay is enabled, a suggested video will automatically play next.

Up next

to add this to Watch Later

Add to

Loading playlists...