- Community Home
- >
- Networking
- >
- Software Defined Networking
- >
- Re: Minimum application?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2013 04:28 PM
12-05-2013 04:28 PM
Minimum application?
I've successfully created an application, initially based on the gen-sdn-app script output, which does a fair number of openflow things, such as having listeners for switches, messages, and packets; setting flows based on a number of fields; and responding to incoming packets forwarded to the controller in order to set actions on those packets.
What I would like to do is to shrink down all of the extraneous stuff, so that I have the basic functionality of the application, for demonstration purposes. The gen-sdn-app script however gives me many projects - api, model, rs, and ui. For prototyping, or for training or for demonstration, those other projects are possibly not necessary.
I'm wondering if anybody knows how to trim this application down to the bare minimum - i.e., just the 'business logic' project. I can try peeling stuff away, but I'd like to know what files I'd need to modify in order to make this as simple and minimal as possible, while still including the openflow functionality I've described.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-11-2013 01:58 AM
12-11-2013 01:58 AM
Re: Minimum application?
Some thoughts that might be helpful-
In the bin directory of HP SDN SDK folder (i.e. some_location/hp-sdn-sdk-2.0.0/bin/) there is a script file gen-sdn-app. In that script near line 63 you can remove the modules that you don’t want to be in your minimum application
gen-sdn-app
…
…
for module in root model api bl rs ui app; do #line 63
…
…
Modified code can be as below-
…
for module in root api bl app; do
…
After modification and running the script just check that the application is building successfully i.e. mandatory basic modules should be present there.
Alternatively you can also create the required modules manually(without script) as per the instruction in the SDN programming guide.
http://h20628.www2.hp.com/km-ext/kmcsdirect/emr_na-c04003169-2.pdf [page 123] talks about Business Logic part.
Thanks.