netgroup-polito / frog4-sdn-do Goto Github PK

The documentation should say that, in the NFFG, priorities higher than 40000 must be used.

According to @DavideXX92 , sometimes, when the SDN-DO tries to configure an ONOS-application just activated, it seems that the application is not yet activated.

This may be fixed by querying (to ONOS?) the status of the application before pushing the configuration.

This description is a bit generic, because no further analysis about the bug has been done so far.

The northbound API should be changed so that it is the same of the northbound API of the FROG orchestrator.

@gabrielecastellano Farman will take care of this, although it is possible that he well have some questions for you.

The repository should contain a file like this one https://github.com/netgroup-polito/frog4-openstack-do/blob/master/README_LAUNCH_VNF.md (it refers to the OpenStack domain orchestrator), which describes all the steps needed to deploy a VNF in the SDN domain.

Please detail in the configuration file the meaning of this flag https://github.com/netgroup-polito/frog4-sdn-do/blob/master/config/default-config.ini#L110 and the reason why it exists.

Now it says if enabled, nffg and description must call interfaces with it's name instead of port name. You could put at least an example in order to make it more clear.

In the JOLNET it must be false, while on a mininet setup it must be true.

I'm trying to deploy a graph on a network consisting by two switches directly connected s1<->s2.
The switches are up, but the link between them is down.

In fact, in the log of the SDN-DO, I see the message cannot find a link between S1 and S2.
However, the SDN-DO returns 202 - Graph correctly deployed, as everything was fine.

Currently the openflow-DO reads the local file that tells which resources are available.
However, if those resources change (e.g., a VLAN is used in an endpoint), their description is not updated and re-sent to the message broker.
This creates troubles for the upper layer orchestrator, as it cannot know which resources have already been consumed, hence some decisions may be wrong.

I propose a [jolnet] section, which contains the following fields:

• jolnet = false (true)
• available_ids = 280-289,62,737,90-95,290-299,13-56,92,57-82

This last field is currently in the [vlan] section, which would disappear.

I think that this organization, which puts togeter all the information related to the jolnet, is more clear.

The script expects a username, a password and a tenant ID.
The tenant ID should be a number that corresponds to a tenant already added in the Tenants table.
In my opinion, the script should expect a name as tenant. Then, if this tenant does not exist in the Tenants table, it adds it and assigns to this tenant an internal ID.

Then, I would like to use a command like
python3 -m scripts.add_user ivano-usr ivano-pwd -t myBeatiful-tenant -m [email protected]

Then it is the scripts that inserts myBeatiful-tenant in the tenants table.

This is how the add user scripts work in the OS-DO and in the FROG orcehstrator.

Please, extend this example https://github.com/netgroup-polito/frog4-sdn-do/blob/master/config/description.json with information about VLANs.
I mean, extend the description so that it includes an endpoint that supports the VLAN.

@gabrielecastellano , according to @farmanullahcs there is some code that is useless.
Can he remove this code? Of course, he works in a branch; the merge into the master will be done only after that we checked that everything still works fine.

Please, write a script to create a new user, then add the proper documentation here https://github.com/netgroup-polito/frog4-sdn-do/blob/master/README_INSTALL.md#how-to-create-new-user

On master
https://github.com/netgroup-polito/frog4-sdn-do/blob/master/do_core/do.py#L514
It does not require any input but it given on
https://github.com/netgroup-polito/frog4-sdn-do/blob/master/do_core/do.py#L75
https://github.com/netgroup-polito/frog4-sdn-do/blob/master/do_core/do.py#L140

The northbound API should use POST for the creation of a graph, PUT for the update

The new code allows to implement NF by exploiting onos applications. However, in the case of a path containing a NF, flow-rules instantiation are demanded to the application itself, so the old code that manages vlan endpoints at the begining/end of the path is not used.

Specify the allowed options in the following items:
controller_name = ...
odl_version= ...

Document more the following items:

• What does "oo" mean in the command "oo_console_print"? Which console are we referring to?

Rename following item:

• dump_file ==> database_name

Modify config file as follow:
log_level= [SET OF LEVELS THAT CAN BE USED to log things; such as "debug", "info", "warning"]
detached_mode= true/false [if true, REST commands are printed on screen and are not actually passed down to the underlying orchestrator]

Why do we need the tenant field in the database https://github.com/netgroup-polito/frog4-sdn-do/blob/master/README_INSTALL.md#create-the-sql-database ?

Is it necessary or can we remove it?

@farmanullahcs changed (alredy in the master repositories) the API, then the domain orchestrator does not receive anymore the tenant parameter.

Then I think that the database could be simplified without this field.

After this commit 62f83d6 the sdn-do is not able to create and initialize a log file. I tried to move the load_configuration() method back to the config.py and it worked.

Missing documentation when using functional capabilities on ONOS where it is needed to install an additional application on the controller