• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Learning OpenStack Networking: Use case for developers

Ranch Hand
Posts: 65
PHP Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi James,

Can you give an example when a developer or development team should consider using OpenStack Networking? I'm not very familiar with the concept.

Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Carl,

OpenStack Networking shouldn't be considered a standalone product item that a developer might consume, rather, it's one piece of a larger platform that one consumes when deploying virtual machine instances. If you're developing an application, whether it be hosted on a single VM, in a traditional 3-tier design, or across containers on multiple VMs, you will need to understand the capabilities of OpenStack Networking and related API so that you can build out the (virtual) networks, subnets, routers, ACLs, etc. accordingly to support your application.

The book provides information to the cloud architect/operator on how to properly install OpenStack and related networking components, and also provides information to the cloud user/application developer on how to interact with the API and build the virtual network objects.  As a user, you may be presented with pre-existing networks setup by the operator and never need to venture any further. Other users may be required to setup one or more virtual routers, networks, ports, etc. depending on the needs of their application and/or virtual machine instance(s), as the one-size-fits-all approach may not be appropriate for their use case.

I hope that helps!

My first bit of advice is that if you are going to be a mime, you shouldn't talk. Even the tiny ad is nodding:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic