I’m going to define the Private Catalog the way we think it should be. It’s to enable service producers and cloud admins to control distribution of solutions. We want to ensure internal compliance and governance and we want solutions to be discoverable within your enterprise– and, of course, easily deployable. So the words control, compliance, governance, discoverable– so those are the key things that I want you to take away from this session today and those are the pillars that we used in order to actually build the Private Catalog. So I’m going to do things a little different today. Instead of giving you a bunch of slides of how great this is and all the features and functionality and everything, I want to tell you a little bit of a story.
We’re going to walk through it and show you how a fictional enterprise might actually leverage the Private Catalog. So there’s a company called ACME Game Studio. So ACME has about 500 people. They’ve been around for a few years. They’ve got a huge market share on game development on mobile devices. So they develop for iOS. They develop for Android, Windows Phone, Nintendo devices– anything you can think of. So these guys basically have an IT environment where they develop virtual machines for their dev and test environments. So the way it works is, a developer at ACME will go find the right VM that they need to develop their product or their feature or their bug fixes. They’ll deploy that. That VM actually contains all the SDK tools, their build tools, integrations with their build lab– everything’s there. So they can go ahead, fix it, then deploy the test VM.
The test VM’s got to contain all the emulators that they need in order to actually test their bug fixes or their features and if everything looks good, they’ll go ahead and check it in and then shut down the machines. That way, they don’t spend a lot of money. They don’t leave machines idle all the time and that’s the environment that they are actually using. There was a wiki. There’s no wiki anymore. He doesn’t know what’s going on. He has to ask around, ask people, ask coworkers, phone a friend. He just doesn’t know what he needs to do. So Darryl basically just doesn’t care. He just launches his VMs, goes, fixes his bugs, and then just keeps it running. So he’s constantly causing a lot of money to be wasted while his VMs are actually just being left around and because the tools keep going updated a lot, anytime he makes a change, he checks it in– he’s making a huge risk that he’s going to break the build.
So when he does break the build, then he’ll go find the right VM, go code for his change, go test it, and then check that in, causing a couple of delays for everyone else, blocking everyone in the pipe. So not really great. So does this sound familiar to you guys? Do you guys handle this? I see a lot of nodding heads. Good. So let’s go try to help Andy fix this. So I’m going to actually do a demo of the live bits. I mentioned that we actually shipped the alpha last week. So I’ll be running the real thing and showing you guys how Andy’s going to actually fix some of these problems. Can you guys switch over? Cool. All right. So I’m actually logged in as the ADME acmin– sorry, the ACME admin and to get to the Private Catalog, on the left nav was the Private Catalog. So what you’re seeing here is what we call the zero state. So you’ve got nothing in here. This is the Private Catalog. There’s nothing for you to see, because we haven’t added anything.