Open Stack Integration with OnePK

[softnet706]

Hello,

I am trying to understand, design and test a use case for integrating Open Stack Integration with OnePK. Currently we have All-in-One Pk and ODL VMs on ESXi hosts interfaced to physical/virtual network infrastructure southbound(Cisco IOS and vIOS routers/switches) and to be integrated to Open Stack systems Northbound. For Open Stack, the plan is to use Mirantis Open Stack with Red Hat Linux Open Stack Distribution as well as other open stack distributions.

I have the following queries:

1. Is there a onePK plugin available on OpenStack via the Neutron/Nova capabilities within OpenStack.

2. Can we run OnePK instances within the Open Stack compute node to replicate the OnePK VMs on ESXi hosts?

3. Also understand that tools like Puppet on Open Stack can be leveraged to automate configuration and Management.

What is the best way to go about integrating ( using a few or all of the above) or using elements of OnePk to program network elements from Open Stack.

Thanks and Regards,

Mohan

[Joe Clarke]

Thanks for your interest in onePK, Mohan.  I'll try and address your individual points.

1. No.  There is no OpenStack plugin for onePK today in that there is no Neutron plugin that will allow it to speak onePK RPCs.
2. This is not supported today.  The only supported means of running the IOSv instances is via the all-in-one VM environment's vmcloud infrastructure.  We have a product in the works called Cisco Modeling Labs (CML).  This is based on OpenStack, and provides images that allow you to run IOSv as well as other virtual operating systems (e.g., XRv, IOSXEv, NXOSv) within an OpenStack environment.  That environment uses KVM at the moment.  CML is slated for release next month as I recall.
3. The Nexus 9K can leverage Puppet.  There is also work underway on a Puppet agent for other NX-OS platforms.

OnePK isn't geared toward provisioning at the moment.  Meaning the device changes introduced via onePK do not persist once the application disconnects.  So your OS plugin would need to remain connected to the device to continue to provide the desired operational state.  If you want more persistence, one option is to consider using the VTY Service Set in onePK for the time being to interact with the CLI to make changes (while using other APIs to gather statistics).  These changes can then be persisted as with other configuration.

[softnet706]

Hi Joseph,

Thanks very much indeed and that is really helpful information regarding using VTY service sets in onePK for more persistence. On the same note, what we were planning to achieve is to discover the topology of a network ( using the topology API) from a Mobile client( ipad) for example connected via 3G to OpenStack and the underlying the ESXi infrastructure, and to perform various actions on the topology discovered via Open Stack. So it looks like currently we have to directly map this information from the Mobile client to the All-in-one PK on ESXi until CML is available. By the way are there are any Java/OnePK API's that can be instantiated from mobile clients (ipad or android for example) to discover Cisco routers and switches?

Thanks and Regards,

Mohan