The quantum name was changed due to a settlement on a trademark 
infringement.

https://answers.launchpad.net/launchpad/+question/231396

The right thing to do here would be to rename the modules, but keep them 
backward compatible via import trickeration.

Brad

On Thursday, December 5, 2013 3:46:18 PM UTC-5, Michael DeHaan wrote:
>
> We will not be renaming modules for this,
> There may be some grouping in a subcategory in
> The future.
>
> -- Michael
>
> On Dec 5, 2013, at 1:00 PM, Bob Tiernay <[email protected] <javascript:>> 
> wrote:
>
> Why not rename all plugins to os_* or openstack_*, including those of 
> keystone_*, nova_*? This avoids any future renames as well. I think it 
> might also aid newcomers like myself that use OpenStack, but aren't 
> familiar with the underlying components.
>
> Cheers,
>
> Bob
>
> On Tuesday, 29 October 2013 21:53:26 UTC-4, Michael DeHaan wrote:
>>
>> It's deprecated in a future release that not everyone is running.
>>
>> We are going to leave this named Quantum and I'm fine with a try/except 
>> here.
>>
>> It's easy, it keeps everything working, it avoids bloating the module 
>> space.
>>
>> "a few weeks in the repository..."
>>
>> People will have live quantum deployments for another year in many cases. 
>>   It's just a name.
>>
>>
>>
>>
>> On Tue, Oct 29, 2013 at 7:01 AM, Christian Berendt 
>> <[email protected]>wrote:
>>
>>> Then remove the quantum_* plugins like suggested. Quantum is deprecated. 
>>> The name in the upstream is Neutron. Why should we keep the deprecated name 
>>> in Ansible? For backward compatibility we could keep the quantum_* plugins 
>>> a few weeks in the repository...
>>>
>>> And it's not the same purpose. The quantum_* plugins are not longer 
>>> usable with the latest release of OpenStack (Havana), because there is not 
>>> longer a python-quantumclient. Only python-neutronclient...
>>>
>>> Christian.
>>>
>>> Am Dienstag, 29. Oktober 2013 12:41:14 UTC+1 schrieb Matt Martz:
>>>>
>>>> I’m in agreement with Machael here.  There are currently 7 quantum_* 
>>>> modules.  If you duplicate them, you now have 14 modules largely for the 
>>>> same purpose.  That really clutters up the module index.
>>>>
>>>> -- 
>>>> Matt Martz
>>>> [email protected]
>>>>  
>>>> On October 29, 2013 at 4:03:29 AM, Christian Berendt (
>>>> [email protected]) wrote:
>>>>
>>>> Yacine Kheddache: That's exactly what I want to do and what I proposed 
>>>> in my pull request: https://github.com/ansible/ansible/pull/4695. 
>>>>
>>>> Michael DeHaan: Does this work for you? We keep the old modules for 
>>>> backward compatibility and will use the new modules (neutron_*) for the 
>>>> future. Users can then rewrite there playbooks when upgrading to Grizzly 
>>>> or 
>>>> Horizon.
>>>>
>>>> Christian.
>>>>  --
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "Ansible Project" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to [email protected].
>>>>
>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>
>>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Ansible Project" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>
>>
>> -- 
>> Michael DeHaan <[email protected]>
>> CTO, AnsibleWorks, Inc.
>> http://www.ansibleworks.com/
>>
>>   -- 
> You received this message because you are subscribed to the Google Groups 
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to