Open Stack

Hi Christoph,

This is a great idea and a tool I think others would be very interested in
having.

Now the question that I have to you and everyone else, is within the
Operators community how would we capture this information so we could open
up dialogue with both the Neutron and Nova teams?

--Joe

On Tue, Mar 29, 2016 at 11:43 AM, Christoph Andreas Torlinsky <
christoph at nuagenetworks.net> wrote:

> Hi Joseph, we would propose a migration tool for getting the NOVA
> networking database information into mapping it Neutron,
> as we are seeing an increasing demand to "upgrade" from Nova Networking to
> an OpenStack Neutron and SDN 3rd Party based
> model for Cloud Computing amongst our installed base of OpenStack
> customers, some of whom grew out of Nova networking and it's
> limits in leveraging VLANs.
>
> I also caught sight of the recent write ups here , which seem to point in
> the same direction actually, in lieu of adoption of Liberty from
> older release:
>
>
> http://docs.openstack.org/liberty/networking-guide/migration-nova-network-to-neutron.html
>
> Any tooling to make this easier as a migration process, we (me) are keen
> to engage and help,
>
> Let us know if anyone else is on the same level working on things,
>
> c
>
>
> Christoph Andreas Torlinski
>
> +44(0)7872413856 UK Mobile
>
> christoph at nuagenetworks.net
>
> On 26 March 2016 at 20:47, Joseph Bajin <josephbajin at gmail.com> wrote:
>
>> Operators,
>>
>> At the last OSOps Tools and Monitoring meeting, we had mriedem (Nova
>> Team) talk with us about a proposal that they are working on. The Nova team
>> would like to abandon the use of a wish-list as it has grown to an
>> unmanageable size.  They have posted a few times to both the operators list
>> [1] as well as the developers list [2] about their idea.  They would like
>> to work with us operators to find the best way to get our ideas into their
>> prioritization list. At the mid-cycle and summit meet-ups, we continue to
>> create etherpads [3] that make mention to the troubles we have, as well as
>> the work we have done to overcome them. These are examples of the work that
>> the NOVA team would like to hear about.
>>
>> I'd like to gather some ideas and thoughts from the operator community on
>> not only the NOVA proposal but ways that we could get the feedback we
>> create each cycle to each of the respective projects.  One idea that I have
>> is using the OSOps repo as a way for us to gather and track these wishlist
>> type of items.  Then the OSOps working group could be used to help try get
>> these worked on.
>>
>> I'd love to get help and hear ideas from others about how we could
>> improve and build on this process. Please let me know your thoughts.
>>
>> Thanks
>>
>> Joe
>>
>>
>> [1]
>> http://lists.openstack.org/pipermail/openstack-operators/2016-March/009942.html
>> [2]
>> http://lists.openstack.org/pipermail/openstack-dev/2016-March/089365.html
>> [3] https://etherpad.openstack.org/p/operator-local-patches
>>
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160405/a2ee97b8/attachment.html>