EMC will choose what code to package into ViPR Controller based on EMC business needs (e.g. call home).

Good Morning!  Thank you for joining our Ask the Experts session. Our SMEs are now standing by to take all your questions. Let’s make of this thread an informative and productive resource so that it could help ECN members today and in the weeks to come.

At this point I would like to get this discussion kicked off. Your questions are now welcome!

Hello and welcome to our Ask the Expert event today, which is focused on the recent EMC ViPR Controller announcement at EMC World…EMC ViPR Controller will now be developed in the open source community, code named CoprHD.  This discussion will help you better understand what open source is, and what this means to EMC and to the future of ViPR Controller.

So let’s get started.  First let’s start by our subject matter experts to describe how they became involved with this project?

Hi Julio Colon here...

I became involved in the project given my long time involved with ViPR.  I have touched many areas of the product (provisioning, security, UI and APIs), the later been the one that have got me in front of many large customers in need for a solution like the one we are offering with ViPR.  I got asked to help with CoprHD and I think is one of the most exiting news we delivered at EMC World.  CoprHD is what has been needed for a very long time in the storage work.  A single open solution that will remove the complexity of managing heterogeneous storage arrays.   I can't wait to see what the development community will do to make storage management one of the most attractive area to be involved today.

Hello all -

I was very excited to see this announced during the keynote at EMC World, great decision!

I'm wondering if the final decisions have been made about exactly which ViPR components are included in CoprHD.  Are things like the SMI-S provider going to be open source as well?  If so, what's NOT included?

Thanks,

Mike Horgan

We're pretty much opening up everything in the controller that we can.

The SMI-S provider is not part of ViPR so we can't open that up. We'll open the source for the SMI-S driver, which is part of ViPR.

Also, there are a few things that won't work the same since it wouldn't really apply. For example, licensing, and the call home functionality should not be the same as in ViPR since this is CoprHD. Also, we can't legally give out libraries that we use that are not open source.

I'll make sure to update the FAQ in the wiki (https://coprhd.atlassian.net/wiki/) and add a full list of anything that doesn't end up being open for whatever reason.

Thanks!

Great, thanks Ura. It sounds like EMC is really going about this the right way.  And the wiki page looks like it will be a great resource as well.

Best Regards,

Mike Horgan

Ura,

is this EMC's first "official" foray into open source realm ? How do you perform QA on code committed by outside contributors ?  Security concerns ?

Thank you guys for the awesome questions.

I wanted to ask about the name Project CoprHD.  What is CoprHD?