OpenNaaS

OpenNaaS 0.19 released

Manel Jara — Tue, 23 Apr 2013 15:00:21 +0000

The OpenNaaS development team is proud to announce the OpenNaaS 0.19 release.

During this period of time, the development team had three main goals:

integrate authentication within OpenNaaS architecture
start adoption of IPv6
improvements and correction of bugs

The authentication is needed for the demarcation in UC2 and support of IPv6 was an issue that was needed to be addressed at some point, but a request from customer has pushed forward this task.

There were also some bugs and improvements reported that have been solved or updated, in order to have a more user-friendly environment and setup.

Known issues

Change in descriptors! The adoption of IPv6 in router resource has brought a change in the capabilities. Now, there is one capability called IP instead of the “old” capability IPv4. If you use an old descriptor an error message like the following will appear in your platform when trying to start the resource xxx: “[ERROR] Cannot start resource router:xxx: Factory not found for capabilities of type: ipv4″.

It has been found a problem with a timeout when creating a new vCPE. It might occur that after finishing the creation of a vCPE a message error could appear saying that “the virtual CPE coulnd’t be created because it already exists”. That’s not exactly true and the new VCPE can be accessed by ommiting the error message and clicking the home button. The vCPE created will appear in the menu and it can be setup without any further problem.

Following you will find the complete list of changes, together with instructions for getting and using the release.

Release Notes – OpenNaaS – Version OpenNaaS 0.19

Bug

[OPENNAAS-905] – SPF does not always return mapping with shortest path links

Improvement

[OPENNAAS-893] – Clean code in mapping algorithm

Story

[OPENNAAS-931] – As an OpenNaaS administrator I want only authenticated users to access resources
[OPENNAAS-933] – Support IPv6 in router resource

Technical task

[OPENNAAS-925] – Integrate Spring Security framework in OpenNaaS
[OPENNAAS-932] – Basic secured application (without ACL) (with usr/pwd or token)
[OPENNAAS-934] – IP
[OPENNAAS-935] – OSPF
[OPENNAAS-936] – GRE
[OPENNAAS-937] – Static route
[OPENNAAS-938] – BGP

Downloads

Linux - opennaas-0.19.tar.gz (125 Mb)
Windows - opennaas-0.19.zip (125 Mb)
vCPE web client- opennaas-vcpe.war (24 Mb)

You can get more information on download or getting the source code in the OpenNaaS download page

Documentation and user support

There are two previous posts that explain how to deploy a vCPE and how to operate the vCPE factory web application that will be useful to anyone interested in OpenNaaS.

Please check the rest of documentation here.

Don’t hesitate to use our mailing lists if you need support

Bug reporting

Mantychore FP7 project members can issue a bug ticket directly at:

http://jira.i2cat.net:8080/secure/CreateIssue!default.jspa

OpenNaaS 0.18 released

Manel Jara — Tue, 02 Apr 2013 08:44:57 +0000

The OpenNaaS development team is proud to announce the OpenNaaS 0.18 release.

During this period of time, the development team has been working on providing two main features for the vCPE web client:

create multiple virtual CPEs given the physical structure.
integration with JBoss.
create new template of Multiple Network Support scenario.

From the GUI, UC2 template can be selected and executed against OpenNaaS as a network administrator. Therefore, two different scenarios can be created using the web client, that implement UC1 and UC2, single provider with backup and mutiple network providers.

There were also some bugs and improvements reported that have been solved or updated, in order to have a more user-friendly environment and setup.

Known issues

Following you will find the complete list of changes, together with instructions for getting and using the release.

Release Notes – OpenNaaS – Version OpenNaaS 0.18

Bug

[OPENNAAS-848] – Wrong neighbour address in vCPE BGP configuration
[OPENNAAS-850] – vCPE Factory home page doesn’t show button style
[OPENNAAS-908] – GUI don’t show the correct VRRP Ip Address
[OPENNAAS-912] – Returning page when failing change in VRRP
[OPENNAAS-916] – When VRRP is changed the returned view doesn’t have buttons

Improvement

[OPENNAAS-853] – Move properties to platform/etc using ConfigAdminUtils like in AbstractCapability
[OPENNAAS-910] – Change header literals from properties to know if the language has actually changed
[OPENNAAS-913] – Missing popup windows asking for confirmation in VRRP change address.
[OPENNAAS-915] – Add progress bar dialog to all user actions going to opennaas

Story

[OPENNAAS-872] – QA – Create checklist to test
[OPENNAAS-875] – Integrate OpenNaaS into Junos Space
[OPENNAAS-877] – Technical documentation for OpenNaaS architecture

Technical task

[OPENNAAS-854] – Definition of template views
[OPENNAAS-856] – Suggests physical infrastructure
[OPENNAAS-860] – Suggest logical infrastructure for GUI
[OPENNAAS-866] – Implement model builder MP-vCPE template – elements
[OPENNAAS-867] – Implement model builder MP-vCPE template – routing
[OPENNAAS-868] – Implement builder MP-VCPE template – elements
[OPENNAAS-869] – Implement builder MP-VCPE template – routing
[OPENNAAS-874] – Make Sp-vCPE template configure BGP properly from user input
[OPENNAAS-879] – OpenNaaS internal design documentation
[OPENNAAS-880] – Integrate an OSGi bundle in JBoss 7.1
[OPENNAAS-881] – Integrate an OSGi bundle in JBoss 7.1 with dependencies
[OPENNAAS-882] – Integrate OpenNaaS in JBoss 7.1

Downloads

Linux - opennaas-0.18.tar.gz (107 Mb)
Windows - opennaas-0.18.zip (107 Mb)
vCPE web client- opennaas-vcpe.war (24 Mb)

You can get more information on download or getting the source code in the OpenNaaS download page

Documentation and user support

There are two previous posts that explain how to deploy a vCPE and how to operate the vCPE factory web application that will be useful to anyone interested in OpenNaaS.

Please check the rest of documentation here.

Don’t hesitate to use our mailing lists if you need support

Bug reporting

Mantychore FP7 project members can issue a bug ticket directly at:

http://jira.i2cat.net:8080/secure/CreateIssue!default.jspa

OpenNaaS 0.17 released

Manel Jara — Mon, 11 Feb 2013 11:45:20 +0000

The OpenNaaS development team is proud to announce the OpenNaaS 0.17 release.

During this period of time, the development team has been working on providing two main features for the vCPE web client:

choose different physical and logical structure where a virtual CPE will be created.
create multiple virtual CPEs given the physical structure.

There were also some bugs and improvements reported that have been solved or updated, in order to have a more user-friendly environment and setup.

Following you will find the complete list of changes, together with instructions for getting and using the release.

Release Notes – OpenNaaS – Version OpenNaaS 0.17

Story

[OPENNAAS-826] – As a GUI user I want to be able to create multiple vCPEs using the same physical infrastructure
[OPENNAAS-827] – As a GUI user I want to be able to create vCPEs of different shapes (using different templates)

Technical task

[OPENNAAS-828] – GUI physical view asks OpenNaaS for a suggested physical infrastructure mapping, and displays it.
[OPENNAAS-829] – GUI logical view should obtaing physical infrastructure data from the physical infrastructure view
[OPENNAAS-830] – GUI logical view should obtain a suggestion from opennaas
[OPENNAAS-831] – Add loopback interfaces to GUI view
[OPENNAAS-832] – Delete unrequired properties and properties files.
[OPENNAAS-833] – Improve logical infrastructure suggestions in vlans and units.
[OPENNAAS-834] – Improve validators and isFree()
[OPENNAAS-835] – vCPEResource: Move capabilities out of builer (vrrp, ips) and make client call new ones.
[OPENNAAS-836] – Refactor builder logic into functional classes to help reusing code
[OPENNAAS-837] – Create fake template to test
[OPENNAAS-838] – Builder capability get the required builder
[OPENNAAS-839] – Create a common interface for all builders
[OPENNAAS-840] – Builder logic depends on a template. One builder per template.
[OPENNAAS-841] – GUI template selector
[OPENNAAS-842] – Add IPaddress ranges to GUI
[OPENNAAS-843] – Assign different VRRPGroup to each VCPE

Downloads

Linux - opennaas-0.17.tar.gz (107 Mb)
Windows - opennaas-0.17.zip (107 Mb)
vCPE web client- opennaas-vcpe.war (24 Mb)

You can get more information on download or getting the source code in the OpenNaaS download page

Documentation and user support

There are two previous posts that explain how to deploy a vCPE and how to operate the vCPE factory web application that will be useful to anyone interested in OpenNaaS.

Please check the rest of documentation here.

Don’t hesitate to use our mailing lists if you need support

Bug reporting

Mantychore FP7 project members can issue a bug ticket directly at:

http://jira.i2cat.net:8080/secure/CreateIssue!default.jspa

How to operate OpenNaaS vCPE application

Isart Canyameres — Fri, 08 Feb 2013 14:00:47 +0000

Following my colleague’s post on how to deploy the vCPE application, this one covers how to use the application for deploying vCPEs on top of your physical infrastructure.

This post assumes following statements. Indications on how to achieve them can be found in how to deploy the vCPE application post.

Assumptions:

There is an OpenNaaS platform already deployed and running in a server which has access to the physical infrastructure to manage.
There is a vCPE instance already deployed and running in an application server.
vCPE instance has access to the OpenNaaS platform.

And it covers three major steps:

Load physical infrastructure in OpenNaaS
Configure OpenNaaS vCPE extension (in platform)
Create a vCPE (using the GUI)

Step 1: Load physical infrastructure in OpenNaaS

In order to manage physical infrastructure devices should be loaded into OpenNaaS. Please, follow this guide to understand the basics on how to load resources in OpenNaaS.

In testing environments, it is recommended to craft a karaf script to automate the loading of your organisation’s physical infrastructure. More information about karaf and it’s features can be found here.

Step2: Configure OpenNaaS vcpe extension (in platform)

2.1: Configure OpenNaaS vCPE extension with the physical infrastructure to use.

This configuration is currently made by template specifying the correct mappings, although this may change in the future.

2.2: Configure OpenNaaS vCPE extension with mappings for the single provider vCPE template

Templates define a virtual topology and routing configuration.In order to apply a template on top of an existing physical infrastructure, some mapping should be calculated.

This mapping is nowadays driven by some configuration files. More specifically, properties files. These files are in following locations:

/org.opennaas.extensions.vcpe/src/main/resources/templates/template.properties
/org.opennaas.extensions.vcpe/src/main/resources/templates/bgpModel1.properties

Mapping between template values and physical infrastructure components is defined in template.properties, in “Physical Topology” section. This mapping defines which physical elements would OpenNaaS interact with when applying the template, and it is a requirement for the application to work properly. A graphical representation of this mapping, is available in the GUI at step 3.3 of this guide. This representation is shown below. However, the user is not allowed, by now, to change this mapping using the GUI.

Figure1: Physical infrastructure mapping in SP-VCPE template

Logical topology section defines logical elements that would be configured by OpenNaaS when applying the template. This section defines default values. A graphical representation of this mapping, is available in the GUI at step 3.4 of this guide, where the user may change given values.

bgpModel1.properties is used in BGP configuration for vCPE logical routers. Together with physical topology section in template.properties, its content is expected to change between different organisations. Specifically, each organisation should specify its prefix lists named “isp-v4-infrastructure”, and “isp-snmp-clients” which values are not exposed to the GUI user. Some other values in bgpModel1.properties can be modified, those referring to AS numbers and IP addresses, but the rest of the document defines the structure of required BGP configuration, and should not be modified. Please notice that AS numbers and ip addresses will be taken from user input at step 3.4 of this guide, so modifying them has no benefit.

Step 3: Create a vCPE (using the GUI)

This step includes gathering vCPE required data and performing the instantiation of the vCPE in existing physical infrastructure.This step can be reproduced while there are required resources available.

3.1 Log into vCPE application

Launch your browser and point it to the vCPE web application running in your tomcat installation: http:///opennaas-vcpe/Let’s assume > is localhost:8080, which is the default.

You’ll be redirected to the login page http://localhost:8080/opennaas-vcpe/auth/login

Just enter credentials for a user with role ROLE_NOC to access your welcome page.

3.2: Choose a template

After the login page, you’ll be redirected to the home page where a template can be selected. Although more templates are to come, currently, there is one single vCPE template supported. It is the single provider vCPE (SP-VCPE), corresponding to the HEAnet use case in Mantychore project.You may see other templates in the GUI. They are there for testing purposes and do not create an usable vCPE. So makes little sense to use them.

SP-VCPE template creates two logical routers linked between each other. They communicate with a single core router of the ISP for WAN access. Each of these logical routers has a connection through a Bandwidth on Demand (BoD) domain to a port where a client can connect. The link between logical routers is also made through the BoD domain. The template creates the logical routers, requests BoD circuits, assign desired vlans and ip addresses, and configures BGP and VRRP providing desired connectivity.

The minimum set of physical infrastructure required for SP-VCPE template is composed of a core router, a physical router supporting logical routers (fabric), and a BoD domain. Core router must have a link to fabric ones. Fabric links must have links to interfaces administrated by the BoD domain. And finally, the client must have an interface in the BoD domain.

3.3: Check physical infrastructure to use in selected template

In this step, physical infrastructure to be used for the creation of the vCPE is displayed. Assigned valued depend on mappings configured in section 2.2 of this guide.

Physical infrastructure components may be reused in the same template. Meaning that several virtual components may be mapped to a single physical one. (Figure 1 illustrates this by reusing interface ge-1/0/7 in cpe1-gsn, in three backup router interfaces)

3.4: Enter logical infrastructure desired values for selected template

This is the most important step in the creation of the vCPE.OpenNaaS suggests values for most of template required fields, based on defaults given in step 2.2, and internal calculations. (Please notice that IP addresses are not yet suggested dynamically, but taken from defaults. Thus, the user is required to change them manually for each vCPE)

The user is free to change most of this values at will. OpenNaaS will check availability of selected values (e.g. for unit numbers, vlans, and ip addresses) and complain if a selected value is already in use or not available.

Figure2: Logical infrastructure mapping in SP-VCPE template, with check in interface unit.

When the user is happy with assigned values, the instantiation of the vCPE may begin.

3.5: Create the vCPE

With all required data in place, creation of the vCPE starts by pushing the create button.This will cause the GUI to send all gathered data to OpenNaaS, which will generate appropriated configurations and apply required actions to instantiate desired vCPE in existing physical infrastructure.

Step 4: Modify an existing vCPE (using the GUI)
Once a vCPE is created, a NOC user can edit it.
In the edit view, the user can switch between master and backup routers, to make client traffic pass through the backup router, and its down link, instead of using the down link in master router.
In this view, the user can also change vlans, units and IP addresses, but not the physical infrastructure in use.

Users with client role can also log into the application to see already created vCPEs.
Clients are allowed to change some parameters of the vCPE regarding the client parts of it.
Mostly, what clients are allowed to do is changing IP addresses, including the gateway IP address. Once vCPE supports OSPF and other IGPs, the user would also be able to select desired one and activate it. At some point, it is expected that users will be able to configure firewalling policies, too.

How to deploy vCPE

jordi_puig — Fri, 11 Jan 2013 14:00:09 +0000

Requirements:

JRE 1.6

Maven 3.x

Tomcat 6.x

In order to deploy the vCPE application, first of all we need to obtain the binary code of the platform of OpenNaaS and the GUI application. To achieve this step you can follow this tutorial in the section called download.

The platform and the GUI are two separate components:

OpenNaaS platform: It is the framework which gives access to the resources and capabilities in order to manage the network.

GUI: Interface which is connected with the platform and allows the management vCPEs. It is a web application that requires an application server. The web application is not part of the platform, and thus, is shipped separately of its releases (it’s the war file). Nevertheless, GUI source code can be obtained by checking out OpenNaaS sources the same way as for the platform.

To boot up the platform we have to run the file opennaas.bat or opennaas.sh (according to SO). The OpenNaaS console will open.

To boot up the GUI, first we should have an application server installed. In our case we will use a Tomcat server, even though we could run other servers such as Glassfish, JBoss, etc…
We have to deploy the application in the server, therefore we have to copy the opennaas-vcpe.war file in to the webapps directory of the application server. If you have build your own binaries, the war file can be found on $OPENNAAS_ROOT/opennaas/clients/opennaas-gui-vcpe/target/opennaas-vcpe.war

Starting the server, the vCPE application will be deployed automatically.

From this moment we will have the whole vCPE environment installed in our system.

Now we have seen how to configure vCPE in our PC but it is possible to have the platform and GUI in separate environments. We need to change the URL of the web services of the platform and the URL of the GUI requests, so that they coincide.

The platform publishes web services that allow the management of the resources remotely. This is how the GUI communicates with the platform. The URL that we publish the services (in the platform) and the URL that we make requests (GUI) have to be set up if we want to work in separate environments.

Platform URL: It is located in the platform file, opennaas/etc/org.opennaas.cfg the property ws.rest.url, and can be modified as needed. Afterwards the platform has to be restarted in order to get the modifications fixed.

GUI URL: Once the GUI has been deployed in the tomcat server, we need to indicate the URL where the requests will be launched. This URL is in the file, opennaas-vcpe/WEB-INF/config.properties. We need to restart the application server too.

By default, these URls are configured to use localhost.

In the next post we will explain how vCPE works.

OpenNaaS 0.16 Released

Julio Carlos Barrera — Thu, 10 Jan 2013 12:11:38 +0000

The OpenNaaS development team is proud to announce the OpenNaaS 0.16 release.

Release 0.16 main features are the addition of more functionalities to the vCPE GUI like changing VRRP priority or VRRP virtual IP address on routers, the creation of better vCPE GUI validations, the improvement of vCPE GUI user experience and the addition of loopback interfaces support. Minor bugs detected and corrected as well.

Note that this release include the WAR container of the GUI client to manage vCPE using OpenNaaS. We are preparing a blog post explaining how to deploy and run this client. Please check the news section the following week.

Following you will find the complete list of changes, together with instructions for getting and using the release.

Release Notes – OpenNaaS – Version OpenNaaS 0.16

Bug

[OPENNAAS-779] – resource:start doesn’t describe problem if cannot start

Story

[OPENNAAS-614] – Configure loopback interfaces via Logical Router

[OPENNAAS-785] – As a GUI user I want to see all the lines connected in create view

[OPENNAAS-786] – As a GUI user I want adjustments in the “Create” button behaviour

[OPENNAAS-794] – Blend together vCPE models (OpenNaaS – GUI)

[OPENNAAS-798] – As a GUI user I want changes to be made in Client box

[OPENNAAS-804] – As a GUI developer I want to be able to change VRRP configuration atomically

Technical task

[OPENNAAS-615] – Add test unitary to test template

[OPENNAAS-787] – Create button has to be disabled until all data in the form is correct

[OPENNAAS-788] – Change text in “create” button when user is in edit view

[OPENNAAS-795] – Discussion about the changes in model

[OPENNAAS-796] – Change VCPE model and propagate changes in OpenNaaS

[OPENNAAS-797] – Change VCPE model and propagate changes in GUI

[OPENNAAS-806] – Add new capability in vCPE builder to edit VRRP priority

[OPENNAAS-807] – Create new VRRP method – update IP address

[OPENNAAS-808] – Create new VRRP method – change priority

[OPENNAAS-809] – VRRP tests

[OPENNAAS-810] – Complete VRRP parser

[OPENNAAS-811] – Remove BGP configuration

[OPENNAAS-812] – Create loopback interfaces to make BGP work

[OPENNAAS-814] – Add loopback interfaces to vCPE builder

Downloads

Linux -  opennaas-0.16.tar.gz  (112 Mb)

Windows -  opennaas-0.16.zip (112 Mb)

vCPE web application - opennaas-vcpe-0.16.war (25 Mb)

You can get more information on download or getting the source code in the OpenNaaS download page

Documentation and user support

Please check our documentation here.

Don’t hesitate to use our mailing lists if you need support

Bug reporting

Mantychore FP7 project members can issue a bug ticket directly at:

http://jira.i2cat.net:8080/secure/CreateIssue!default.jspa

OpenNaaS 0.15 Released

Manel Jara — Fri, 28 Dec 2012 11:05:29 +0000

The OpenNaaS development team is proud to announce the OpenNaaS 0.15 release.

Release 0.15 was presented in IEEE CloudCom 2012 in Taipei, Taiwan last December 4th. It completes the GUI introduced on last release by adding new protocols to the vCPE configuration: BGP and VRRP. It also includes an improved error handling that checks if interfaces and VLANs are available and a representation of the physical layout necessary to create a vCPE.

In order to run the new GUI and create a vCPE you need to have the physical infraestructure with an specific setup. A vCPE needs a master router and a backup router, both connecting to the client-end using autoBAHN. The following resources, as an example, will need to be added to OpenNaaS before attempting to create a vCPE.

resource:create $descriptors.path/myre.descriptor protocols:context router:myre netconf password ssh://xxxx:yyyy@example.com/netconf resource:start router:myre resource:create $descriptors.path/cpe1-gsn.descriptor protocols:context router:cpe1-gsn netconf password ssh://xxxx:yyyy@example.com/netconf resource:start router:cpe1-gsn resource:create $descriptors.path/autobahn.descriptor protocols:context bod:autobahn autobahn noauth http://example.com/autobahn resource:start bod:autobahn

Following you will find the complete list of changes, together with instructions for getting and using the release.

Release Notes – OpenNaaS – Version OpenNaaS 0.15

Improvement

[OPENNAAS-731] – Handle errors at GUI level when OpenNaaS cannot complete execution

[OPENNAAS-748] – Check if resources are available before commiting changes

[OPENNAAS-771] – Move the create and start VCPENetwork

Story

[OPENNAAS-20] – As a user I want to configure VRRP on an interface

[OPENNAAS-541] – Add BGP support to CIM model

[OPENNAAS-742] – As a GUI user I want to have a map to see and edit vCPEs

[OPENNAAS-744] – As a GUI user I want a template that set ups vCPE UC1 scenario

[OPENNAAS-749] – As a user I want know if a given resource is available

Technical task

[OPENNAAS-723] – update GUI view – create

[OPENNAAS-736] – Add URI for OpenNaaS REST connection in properties file

[OPENNAAS-743] – Validate input fields in the GUI and isFree validate

[OPENNAAS-745] – Add BGP configuration to builder

[OPENNAAS-746] – Add VRRP logic to builder

[OPENNAAS-747] – Add Static Route logic for builder

[OPENNAAS-750] – Create model VRRP – GUI

[OPENNAAS-751] – Create CPE view

[OPENNAAS-752] – Create layout for vCPE view

[OPENNAAS-753] – Add functionality to create a vCPE on vCPE view

[OPENNAAS-755] – Add BGP functionality

[OPENNAAS-756] – Add VRRP functionality

[OPENNAAS-757] – Show BoD links in create and edit views

[OPENNAAS-759] – Setup Junos configuration

[OPENNAAS-760] – VM template

[OPENNAAS-762] – Add to model

[OPENNAAS-763] – Setup Junos configuration

[OPENNAAS-764] – VM template

[OPENNAAS-765] – Parser VRRP

[OPENNAAS-766] – Add VRRP to model

[OPENNAAS-772] – Add list of VCPE in the lateral menu.

[OPENNAAS-773] – Add new down-interfaces for customer

[OPENNAAS-774] – Create model BGP GUI

[OPENNAAS-775] – Add GUI data of BoD interfaces to builder

Downloads

Linux -  opennaas-0.15.tar.gz  (125 Mb)

Windows -  opennaas-0.15.zip (125 Mb)

You can get more information on download or getting the source code in the OpenNaaS download page

Documentation and user support

Please check our documentation here.

Don’t hesitate to use our mailing lists if you need support

Bug reporting

Mantychore FP7 project members can issue a bug ticket directly at:

http://jira.i2cat.net:8080/secure/CreateIssue!default.jspa

OpenNaaS 0.14 Released

Manel Jara — Wed, 21 Nov 2012 11:53:05 +0000

The OpenNaaS development team is proud to announce the OpenNaaS 0.14 release.

Release 0.14 main feature is the creation of a fully operational web application, providing a GUI client which allows a NOC to create a vCPE from a given infrastructure using a web form. It also allows a customer to change the IP address of its resources accommodating the vCPE to its current network. Minor bugs detected and corrected as well.

Following you will find the complete list of changes, together with instructions for getting and using the release.

Release Notes – OpenNaaS – Version OpenNaaS 0.14

Bug

[OPENNAAS-739] – Fail when creating gr interfaces

[OPENNAAS-740] – Messing up vlans in autobahn driver

Tasks

[OPENNAAS-692] – Define vCPE Descriptor

[OPENNAAS-693] – Design and implement JSP view form

[OPENNAAS-695] – Menu vCPE Network

[OPENNAAS-696] – Menu vCPE Network

[OPENNAAS-697] – Create vCPE resource sketelon

[OPENNAAS-698] – Create new vCPE Network model

[OPENNAAS-699] – GUI WF – Create LR + add interfaces + setIP

[OPENNAAS-700] – GUI WF – Create links (no autobahn)

[OPENNAAS-701] – GUI WF – Update topology

[OPENNAAS-703] – GUI WF – Destroy LR

[OPENNAAS-704] – GUI WF – Destroy links

[OPENNAAS-707] – List resources descriptors export to WS

[OPENNAAS-708] – vCPE descriptor persistence

[OPENNAAS-710] – WF – add context and start LR automatically

[OPENNAAS-711] – WF – Create links autobahn

[OPENNAAS-712] – WF – destroy links autobahn

[OPENNAAS-713] – WF – Configure static routes

[OPENNAAS-714] – WF – Deconfigure static routes

[OPENNAAS-734] – Edit capability al vCPENetworkResource to allow IP modification

[OPENNAAS-710] - WF – add context and start LR automatically

[OPENNAAS-711] - WF – Create links autobahn

[OPENNAAS-712] - WF – destroy links autobahn

[OPENNAAS-713] - WF – Configure static routes

[OPENNAAS-714] - WF – Deconfigure static routes

[OPENNAAS-728] - vCPEManager implementation – destroy

[OPENNAAS-727] - vCPEManager implementation – get

[OPENNAAS-726] - vCPEManager implementation – list

[OPENNAAS-722] - GUI-vCPEManager integration – get

[OPENNAAS-721] - GUI-vCPEManager integration – list

[OPENNAAS-720] - GUI-vCPEManager integration – remove

[OPENNAAS-719] - GUI-vCPEManager integration – create

[OPENNAAS-718] - vCPEManager ws

[OPENNAAS-717] - GUI user authentication

[OPENNAAS-716] - vCPEManager implementation – create

[OPENNAAS-715] - vCPEManager interface

[OPENNAAS-732] - Set interface IP range from GUI

[OPENNAAS-733] - Edit IPs from GUI at client end user page

[OPENNAAS-734] - Edit capability al vCPENetworkResource

[OPENNAAS-735] - Create properties for vCPENetwork template

Downloads

Linux -  opennaas-0.14.tar.gz  (125 Mb)

Windows -  opennaas-0.14.zip (125 Mb)

You can get more information on download or getting the source code in the download page

Documentation and user support

Please check our documentation here.

Don’t hesitate to use our mailing lists if you need support

Bug reporting

Mantychore FP7 project members can issue a bug ticket directly at:

http://jira.i2cat.net:8080/secure/CreateIssue!default.jspa

OpenNaaS 0.13 Released

Manel Jara — Thu, 27 Sep 2012 13:46:52 +0000

The OpenNaaS development team is proud to announce the OpenNaaS 0.13 release.

Release 0.13 main feature is the creation of a basic structure of a web application, providing a GUI client which uses most of the functionality of RESTful Web service interface introduced in last release. Minor bugs detected and corrected as well.

Following you will find the complete list of changes, together with instructions for getting and using the release.

Release Notes – OpenNaaS – Version OpenNaaS 0.13

Bug

[OPENNAAS-236] – Stopping and starting resource removes interface information from model

[OPENNAAS-338] – Untagged VLANs are people too

[OPENNAAS-496] – Marketplace support:

[OPENNAAS-517] – The CLI is hanging

[OPENNAAS-674] – When executing OpenNaaS platform, I only see 193 commands

[OPENNAAS-686] – Bamboo doesn’t work for OpenNaaS projects

Improvement

[OPENNAAS-690] – Update Autobahn to use alternative uap.

Tasks

[OPENNAAS-675] – EGI demonstration

[OPENNAAS-676] – Prepare Sprint 0.13 Demonstration

[OPENNAAS-677] – Collect capabilities and functionalities for the GUI

[OPENNAAS-678] – GUI mockup

[OPENNAAS-679] – Technology definition and architecture for the GUI client

[OPENNAAS-680] – Build GUI prototype

[OPENNAAS-681] – Resolve bugs

Downloads

Linux -   opennaas-0.13.tar.gz (125 Mb)

Windows -  opennaas-0.13.zip (125 Mb)

You can get more information on download or getting the source code in the download page

Documentation and user support

Please check our documentation here.

Don’t hesitate to use our mailing lists if you need support

Bug reporting

Mantychore FP7 project members can issue a bug ticket directly at:

http://jira.i2cat.net:8080/secure/CreateIssue!default.jspa

OpenNaaS 0.12 Released

admin — Fri, 03 Aug 2012 11:06:58 +0000

The OpenNaaS development team is proud to announce the OpenNaaS 0.12 release.

Release 0.12 main features include key-authentication and most of the functionality of RESTful Web service interface (pending thorough testing ). Also worth noting is an update of the documentation here.

Following you will find the complete list of changes, together with instructions for getting and using the release.

Complete release changes:

Bug

[OPENNAAS-495] – Error Report : OpenNaaS installation

[OPENNAAS-496] – Marketplace support:

[OPENNAAS-508] – Static ws fails to load

[OPENNAAS-519] – Itests module not found in platform.

Story

[OPENNAAS-163] – As a NOC user I want OpenNaaS to be able to connect to a router using key-authentication.

Technical task

[OPENNAAS-441] – Export all WS using REST

[OPENNAAS-482] – investigate netconf auth

[OPENNAAS-483] – investigate how to auth with ssh

[OPENNAAS-484] – modify PSC to store keys

[OPENNAAS-485] – Use key in netconf connections

[OPENNAAS-486] – implement auth type switch

[OPENNAAS-487] – Update PSM commands to obtain key

[OPENNAAS-488] – Stabilise platform

[OPENNAAS-489] – Export a capability ws with model objects (prototype)

[OPENNAAS-492] – Export PSM using REST and DOSGi

[OPENNAAS-493] – Export Q using REST and DOSGi

[OPENNAAS-497] – Export Chassis capability using REST and DOSGI

[OPENNAAS-498] – Export Gretunnel capability using REST and DOSGI

[OPENNAAS-499] – Export IP capability using REST and DOSGI

[OPENNAAS-500] – Export OSPF capability using REST and DOSGI

[OPENNAAS-501] – Export static capability using REST and DOSGI

[OPENNAAS-502] – Export Connections capability using REST and DOSGI

[OPENNAAS-503] – Export Monitoring capability using REST and DOSGI

[OPENNAAS-504] – Export NetBasic capability using REST and DOSGI

[OPENNAAS-505] – Export NetOSPF capability using REST and DOSGI

[OPENNAAS-506] – Export NetQueue capability using REST and DOSGI

[OPENNAAS-507] – Export L2bod capability using REST and DOSGI

[OPENNAAS-522] – Export macbridge capability using REST and DOSGI

Downloads

Linux -   opennaas-0.12.tar.gz (106 Mb)

Windows - opennaas-0.12.zip (125 Mb)

You can get more information on download or getting the source code in the download page

Documentation and user support

Please check our documentation here.

Don’t hesitate to use our mailing lists if you need support

Bug reporting

Mantychore FP7 project members can issue a bug ticket directly at:

http://jira.i2cat.net:8080/secure/CreateIssue!default.jspa