Orchestrator <-- need to pick a different name?

[Justin Clift]

Hi Mark,

VMware already has a virtualization product called "Orchestrator",
specifically for vCenter which we're supporting:

http://www.vmware.com/products/vcenter-orchestrator/overview.html

Would it be ok for us to pick a different name for ours?

Having the same name, for different software, when both products will
conceivably be used in the same enterprise environments, is going
to make things harder.  Writing guides/docs especially, but also people
doing Google searches and getting wrong product info.

?

Regards and best wishes,

Justin Clift

--
Aeolus Community Manager
http://www.aeolusproject.org

[Hugh O. Brock]

On Tue, Jul 26, 2011 at 01:10:12AM +1000, Justin Clift wrote:
> Hi Mark,
>
> VMware already has a virtualization product called "Orchestrator",
> specifically for vCenter which we're supporting:
>
> http://www.vmware.com/products/vcenter-orchestrator/overview.html
>
> Would it be ok for us to pick a different name for ours?
>
> Having the same name, for different software, when both products will
> conceivably be used in the same enterprise environments, is going
> to make things harder.  Writing guides/docs especially, but also people
> doing Google searches and getting wrong product info.

Well, it's an upstream project. There is no thought of ever
productizing it under that name. Moreover, it's part of Aeolus. Seems
like more-or-less a non-issue to me. Let's sort out whether the
component is even going to exist at all before we worry about whether
it has the right name or not.

--H
> ?
>
> Regards and best wishes,
>
> Justin Clift
>
> --
> Aeolus Community Manager
> http://www.aeolusproject.org
>
> aeolus-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/aeolus-devel

[Mark McLoughlin]

On Mon, 2011-07-25 at 11:26 -0400, Hugh Brock wrote:
> On Tue, Jul 26, 2011 at 01:10:12AM +1000, Justin Clift wrote:
> > Hi Mark,
> >
> > VMware already has a virtualization product called "Orchestrator",
> > specifically for vCenter which we're supporting:
> >
> > http://www.vmware.com/products/vcenter-orchestrator/overview.html
> >
> > Would it be ok for us to pick a different name for ours?
> >
> > Having the same name, for different software, when both products will
> > conceivably be used in the same enterprise environments, is going
> > to make things harder.  Writing guides/docs especially, but also people
> > doing Google searches and getting wrong product info.
>
> Well, it's an upstream project. There is no thought of ever
> productizing it under that name. Moreover, it's part of Aeolus. Seems
> like more-or-less a non-issue to me. Let's sort out whether the
> component is even going to exist at all before we worry about whether
> it has the right name or not.

Yeah, the naming conflict doesn't see like a big deal to me - it would
always be "Aeolus Orchestrator"

But, then again, don't we already have a name for this effort - does
'Audrey' cover the whole concept, or just the guest agent?

Cheers,
Mark.

[Mo Morsi]

I do like the notion of having a 'music' theme to our component names 
(eg conductor), kinda unifies the various sub-projects

How about: harmony, opera, resonance, sonata, symphony, unison, virtuoso

There are alot more here:

http://www.classicalworks.com/html/glossary.html

-Mo

On 07/25/2011 11:10 AM, Justin Clift wrote:
> Hi Mark,
>
> VMware already has a virtualization product called "Orchestrator",
> specifically for vCenter which we're supporting:
>
> http://www.vmware.com/products/vcenter-orchestrator/overview.html
>
> Would it be ok for us to pick a different name for ours?
>
> Having the same name, for different software, when both products will
> conceivably be used in the same enterprise environments, is going
> to make things harder.  Writing guides/docs especially, but also people
> doing Google searches and getting wrong product info.
>
> ?
>
> Regards and best wishes,
>
> Justin Clift
>
> --
> Aeolus Community Manager
> http://www.aeolusproject.org
>
> aeolus-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/aeolus-devel

[steve linabery]

nice top-posting mo ;) /me follows suit

composer and arranger come to mind if we want to pursue this musical theme.

s|e

On Mon, Jul 25, 2011 at 11:36:28AM -0400, Mo Morsi wrote:
> I do like the notion of having a 'music' theme to our component names 
> (eg conductor), kinda unifies the various sub-projects
>
> How about: harmony, opera, resonance, sonata, symphony, unison, virtuoso
>
> There are alot more here:
>
> http://www.classicalworks.com/html/glossary.html
>
> -Mo
>
> On 07/25/2011 11:10 AM, Justin Clift wrote:
> > Hi Mark,
> >
> > VMware already has a virtualization product called "Orchestrator",
> > specifically for vCenter which we're supporting:
> >
> > http://www.vmware.com/products/vcenter-orchestrator/overview.html
> >
> > Would it be ok for us to pick a different name for ours?
> >
> > Having the same name, for different software, when both products will
> > conceivably be used in the same enterprise environments, is going
> > to make things harder.  Writing guides/docs especially, but also people
> > doing Google searches and getting wrong product info.
> >
> > ?
> >
> > Regards and best wishes,
> >
> > Justin Clift
> >
> > --
> > Aeolus Community Manager
> > http://www.aeolusproject.org
> >
> > aeolus-devel mailing list
> > [e-mail]
> > https://fedorahosted.org/mailman/listinfo/aeolus-devel
>
> aeolus-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/aeolus-devel

[Matt Wagner]

On Mon, Jul 25, 2011 at 11:36:28AM -0400, Mo Morsi wrote:
> I do like the notion of having a 'music' theme to our component names 
> (eg conductor), kinda unifies the various sub-projects
>
> How about: harmony, opera, resonance, sonata, symphony, unison, virtuoso

"Virtuoso" sounds like an awesome name for something
virtualization-related, too!

I feel a project rename coming on.

-- Matt

[Dmitri Pal]

On 07/25/2011 03:06 PM, Matt Wagner wrote:
> On Mon, Jul 25, 2011 at 11:36:28AM -0400, Mo Morsi wrote:
> > I do like the notion of having a 'music' theme to our component names 
> > (eg conductor), kinda unifies the various sub-projects
> >
> > How about: harmony, opera, resonance, sonata, symphony, unison, virtuoso
>
> "Virtuoso" sounds like an awesome name for something
> virtualization-related, too!

Just FYI
http://en.wikipedia.org/wiki/Virtuoso_Universal_Server
> I feel a project rename coming on.
>
> -- Matt
> _______________________________________________
> aeolus-devel mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/aeolus-devel