1. z.archive.aaa-dev@lists.opendaylight.org
  2. Messages
   Date   
Re: [SSL-RESTCONF] Query about etc/custom.properties

Ignacio Dominguez Martinez-Casanueva <i.dominguezm@...>
 

Hi Vamsi,

I have faced this same error a long time ago (not in Nitrogen though), but at the time I wasn't able to figure out the root cause. Which ODL version are you using? Nitrogen SR1?

Have you tried cleaning OpenDaylight and restarting the service? I usually follow this procedure (in CentOS):

    rm -rf <odl_folder>/data/ <odl_folder>/journal/ <odl_folder>/instances/

and then:

    systemctl restart opendaylight.service

Afterwards, please check karaf.log and wait until ODL has finished booting.

If this does not solve the problem, I don't know what else you could do. Maybe this thread should be moved to a more related mailing list.

Does anyone know what could be the reason of ODL stuck with "Deploying"?

Best regards,
Ignacio.

On 01.02.2018 11:34, A Vamsikrishna wrote:

Hi Ignacio,

 

I have installed Mdsal-apidocs  feature but it’s showing as “Deploying” which ideally should be “Deployed”.

 

opendaylight-user@root>feature:install odl-mdsal-apidocs

opendaylight-user@root>

opendaylight-user@root>

opendaylight-user@root>feature:list -i | grep -i apidoc

odl-mdsal-apidocs                               | 1.7.0.SNAPSHOT   | x        | Started | odl-mdsal-apidocs                               | OpenDaylight :: MDSAL :: APIDOCS

opendaylight-user@root>

opendaylight-user@root>

opendaylight-user@root>web:list

ID  | State       | Web-State   | Level | Web-ContextPath           | Name

-------------------------------------------------------------------------------------------------------------------------------

179 | Active      | Deploying   | 80    | /auth                     | org.opendaylight.aaa.aaa-shiro (0.7.0.SNAPSHOT)

313 | Active      | Deploying   | 80    | /restconf                 | MD SAL Restconf Connector (1.7.0.SNAPSHOT)

351 | Active      | Deploying   | 80    | /controller/nb/v2/neutron | org.opendaylight.neutron.northbound-api (0.10.0.SNAPSHOT)

441 | Active      | Deploying   | 80    | /apidoc                   | MD SAL Rest Api Doc Generator (1.7.0.SNAPSHOT)

opendaylight-user@root>

opendaylight-user@root>

 

Any suggestions on this ?

 

Thanks,

Vamsi

 

From: Ignacio Dominguez Martinez-Casanueva [mailto:i.dominguezm@...]
Sent: Wednesday, January 31, 2018 5:38 PM
To: A Vamsikrishna <a.vamsikrishna@...>; Ryan Goulding <ryandgoulding@...>; Evan Zeller <ezeller@...>
Cc: aaa-dev@...
Subject: Re: [SSL-RESTCONF] Query about etc/custom.properties

 

Hi Vamsi,

Please make sure you have installed `odl-mdsal-apidocs` feature. It seems the REST endpoint you are trying to access (APIDOCS EXPLORER) is not available in OpenDaylight.

opendaylight-user@root>feature:list | grep apidoc
odl-mdsal-apidocs                                | 1.6.1            | x        | Started     | odl-mdsal-apidocs                                | OpenDaylight :: MDSAL :: APIDOCS

 

If it is installed correctly, you should see from karaf that its API REST service running.

opendaylight-user@root>web:list
ID  | State       | Web-State   | Level | Web-ContextPath           | Name
---------------------------------------------------------------------------------------------------------------------
...

317 | Active      | Deployed    | 80    | /apidoc                   | MD SAL Rest Api Doc Generator (1.6.1)

...

Best regards,
Ignacio.

On 31.01.2018 12:18, A Vamsikrishna wrote:

Hi Ryan / Evan / Ignacio,

 

I am able to make the SSL-RESTCONF work with custom.properties with the same changes I have put in org.ops4j.pax.web

 

That is:

 

org.osgi.service.http.secure.enabled=true

org.osgi.service.http.port.secure=8443

org.ops4j.pax.web.ssl.keystore=configuration/ssl/ctl.jks

org.ops4j.pax.web.ssl.truststore=configuration/ssl/truststore.jks

org.ops4j.pax.web.ssl.password=opendaylight

org.ops4j.pax.web.ssl.keypassword=opendaylight

 

org.ops4j.pax.web remains unchanged.

 

curl seems to be working fine:

 

stack@ubuntu:/etc/openvswitch$ curl -l http://192.168.56.1:8181/restconf/operational/network-topology:network-topology/ --user admin:admin

{"network-topology":{"topology":[{"topology-id":"flow:1"},{"topology-id":"ovsdb:1"},{"topology-id":"netvirt:1"},{"topology-id":"hwvtep:1"}]}}

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$ curl -l -k https://192.168.56.1:8443/restconf/operational/network-topology:network-topology/ --user admin:admin

{"network-topology":{"topology":[{"topology-id":"flow:1"},{"topology-id":"ovsdb:1"},{"topology-id":"netvirt:1"},{"topology-id":"hwvtep:1"}]}}

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

 

But if I try to open in browser I am seeing below errors:

 

 

 

Any idea how to fix this ??

 

Thanks,

Vamsi

 

 

From: A Vamsikrishna
Sent: Wednesday, January 31, 2018 3:55 PM
To: 'Ryan Goulding' <ryandgoulding@...>; 'Ignacio Dominguez Martinez-Casanueva' <i.dominguezm@...>; 'Evan Zeller' <ezeller@...>
Cc: aaa-dev@...
Subject: [SSL-RESTCONF] Query about etc/custom.properties

 

Hi Ryan / Evan / Ignacio,

 

I am able to make SSL-RESTCONF connection by modifying C:\master\distribution\karaf\target\assembly\etc\org.ops4j.pax.web as below:

 

org.osgi.service.http.secure.enabled=true

org.osgi.service.http.port.secure=8443

org.ops4j.pax.web.ssl.keystore=configuration/ssl/ctl.jks

org.ops4j.pax.web.ssl.truststore=configuration/ssl/truststore.jks

org.ops4j.pax.web.ssl.password=opendaylight

org.ops4j.pax.web.ssl.keypassword=opendaylight

 

I am just wondering if there is any way to make the same work with C:\master\distribution\karaf\target\assembly\etc\custom.properties without modifying org.ops4j.pax.web

 

Can you please help me out with this ?

 

Thanks,

Vamsi

 
Question on AAA clustering with Nitrogen

Srini Seetharaman
 

Hi, I recently migrated to Nitrogen from an earlier release. I notice that the odl-aaa-mdsal-cluster feature is not available anymore. As the documentation suggests, do we need to explore out-of-band mechanisms to keep the cluster instance in sync with AAA credentials?

Thanks
Srini.
Re: [SSL-RESTCONF] Query about etc/custom.properties

A Vamsikrishna
 

Hi Ignacio,

 

I have installed Mdsal-apidocs  feature but it’s showing as “Deploying” which ideally should be “Deployed”.

 

opendaylight-user@root>feature:install odl-mdsal-apidocs

opendaylight-user@root>

opendaylight-user@root>

opendaylight-user@root>feature:list -i | grep -i apidoc

odl-mdsal-apidocs                               | 1.7.0.SNAPSHOT   | x        | Started | odl-mdsal-apidocs                               | OpenDaylight :: MDSAL :: APIDOCS

opendaylight-user@root>

opendaylight-user@root>

opendaylight-user@root>web:list

ID  | State       | Web-State   | Level | Web-ContextPath           | Name

-------------------------------------------------------------------------------------------------------------------------------

179 | Active      | Deploying   | 80    | /auth                     | org.opendaylight.aaa.aaa-shiro (0.7.0.SNAPSHOT)

313 | Active      | Deploying   | 80    | /restconf                 | MD SAL Restconf Connector (1.7.0.SNAPSHOT)

351 | Active      | Deploying   | 80    | /controller/nb/v2/neutron | org.opendaylight.neutron.northbound-api (0.10.0.SNAPSHOT)

441 | Active      | Deploying   | 80    | /apidoc                   | MD SAL Rest Api Doc Generator (1.7.0.SNAPSHOT)

opendaylight-user@root>

opendaylight-user@root>

 

Any suggestions on this ?

 

Thanks,

Vamsi

 

From: Ignacio Dominguez Martinez-Casanueva [mailto:i.dominguezm@...]
Sent: Wednesday, January 31, 2018 5:38 PM
To: A Vamsikrishna <a.vamsikrishna@...>; Ryan Goulding <ryandgoulding@...>; Evan Zeller <ezeller@...>
Cc: aaa-dev@...
Subject: Re: [SSL-RESTCONF] Query about etc/custom.properties

 

Hi Vamsi,

Please make sure you have installed `odl-mdsal-apidocs` feature. It seems the REST endpoint you are trying to access (APIDOCS EXPLORER) is not available in OpenDaylight.

opendaylight-user@root>feature:list | grep apidoc
odl-mdsal-apidocs                                | 1.6.1            | x        | Started     | odl-mdsal-apidocs                                | OpenDaylight :: MDSAL :: APIDOCS

 

If it is installed correctly, you should see from karaf that its API REST service running.

opendaylight-user@root>web:list
ID  | State       | Web-State   | Level | Web-ContextPath           | Name
---------------------------------------------------------------------------------------------------------------------
...

317 | Active      | Deployed    | 80    | /apidoc                   | MD SAL Rest Api Doc Generator (1.6.1)

...

Best regards,
Ignacio.

On 31.01.2018 12:18, A Vamsikrishna wrote:

Hi Ryan / Evan / Ignacio,

 

I am able to make the SSL-RESTCONF work with custom.properties with the same changes I have put in org.ops4j.pax.web

 

That is:

 

org.osgi.service.http.secure.enabled=true

org.osgi.service.http.port.secure=8443

org.ops4j.pax.web.ssl.keystore=configuration/ssl/ctl.jks

org.ops4j.pax.web.ssl.truststore=configuration/ssl/truststore.jks

org.ops4j.pax.web.ssl.password=opendaylight

org.ops4j.pax.web.ssl.keypassword=opendaylight

 

org.ops4j.pax.web remains unchanged.

 

curl seems to be working fine:

 

stack@ubuntu:/etc/openvswitch$ curl -l http://192.168.56.1:8181/restconf/operational/network-topology:network-topology/ --user admin:admin

{"network-topology":{"topology":[{"topology-id":"flow:1"},{"topology-id":"ovsdb:1"},{"topology-id":"netvirt:1"},{"topology-id":"hwvtep:1"}]}}

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$ curl -l -k https://192.168.56.1:8443/restconf/operational/network-topology:network-topology/ --user admin:admin

{"network-topology":{"topology":[{"topology-id":"flow:1"},{"topology-id":"ovsdb:1"},{"topology-id":"netvirt:1"},{"topology-id":"hwvtep:1"}]}}

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

 

But if I try to open in browser I am seeing below errors:

 

 

 

Any idea how to fix this ??

 

Thanks,

Vamsi

 

 

From: A Vamsikrishna
Sent: Wednesday, January 31, 2018 3:55 PM
To: 'Ryan Goulding' <ryandgoulding@...>; 'Ignacio Dominguez Martinez-Casanueva' <i.dominguezm@...>; 'Evan Zeller' <ezeller@...>
Cc: aaa-dev@...
Subject: [SSL-RESTCONF] Query about etc/custom.properties

 

Hi Ryan / Evan / Ignacio,

 

I am able to make SSL-RESTCONF connection by modifying C:\master\distribution\karaf\target\assembly\etc\org.ops4j.pax.web as below:

 

org.osgi.service.http.secure.enabled=true

org.osgi.service.http.port.secure=8443

org.ops4j.pax.web.ssl.keystore=configuration/ssl/ctl.jks

org.ops4j.pax.web.ssl.truststore=configuration/ssl/truststore.jks

org.ops4j.pax.web.ssl.password=opendaylight

org.ops4j.pax.web.ssl.keypassword=opendaylight

 

I am just wondering if there is any way to make the same work with C:\master\distribution\karaf\target\assembly\etc\custom.properties without modifying org.ops4j.pax.web

 

Can you please help me out with this ?

 

Thanks,

Vamsi

 
Re: [SSL-RESTCONF] Query about etc/custom.properties

Ignacio Dominguez Martinez-Casanueva <i.dominguezm@...>
 

Hi Vamsi,

Please make sure you have installed `odl-mdsal-apidocs` feature. It seems the REST endpoint you are trying to access (APIDOCS EXPLORER) is not available in OpenDaylight.

opendaylight-user@root>feature:list | grep apidoc
odl-mdsal-apidocs                                | 1.6.1            | x        | Started     | odl-mdsal-apidocs                                | OpenDaylight :: MDSAL :: APIDOCS


If it is installed correctly, you should see from karaf that its API REST service running.

opendaylight-user@root>web:list
ID  | State       | Web-State   | Level | Web-ContextPath           | Name
---------------------------------------------------------------------------------------------------------------------
...

317 | Active      | Deployed    | 80    | /apidoc                   | MD SAL Rest Api Doc Generator (1.6.1)

...

Best regards,
Ignacio.

On 31.01.2018 12:18, A Vamsikrishna wrote:

Hi Ryan / Evan / Ignacio,

 

I am able to make the SSL-RESTCONF work with custom.properties with the same changes I have put in org.ops4j.pax.web

 

That is:

 

org.osgi.service.http.secure.enabled=true

org.osgi.service.http.port.secure=8443

org.ops4j.pax.web.ssl.keystore=configuration/ssl/ctl.jks

org.ops4j.pax.web.ssl.truststore=configuration/ssl/truststore.jks

org.ops4j.pax.web.ssl.password=opendaylight

org.ops4j.pax.web.ssl.keypassword=opendaylight

 

org.ops4j.pax.web remains unchanged.

 

curl seems to be working fine:

 

stack@ubuntu:/etc/openvswitch$ curl -l http://192.168.56.1:8181/restconf/operational/network-topology:network-topology/ --user admin:admin

{"network-topology":{"topology":[{"topology-id":"flow:1"},{"topology-id":"ovsdb:1"},{"topology-id":"netvirt:1"},{"topology-id":"hwvtep:1"}]}}

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$ curl -l -k https://192.168.56.1:8443/restconf/operational/network-topology:network-topology/ --user admin:admin

{"network-topology":{"topology":[{"topology-id":"flow:1"},{"topology-id":"ovsdb:1"},{"topology-id":"netvirt:1"},{"topology-id":"hwvtep:1"}]}}

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

 

But if I try to open in browser I am seeing below errors:

 

 

 

Any idea how to fix this ??

 

Thanks,

Vamsi

 

 

From: A Vamsikrishna
Sent: Wednesday, January 31, 2018 3:55 PM
To: 'Ryan Goulding' <ryandgoulding@...>; 'Ignacio Dominguez Martinez-Casanueva' <i.dominguezm@...>; 'Evan Zeller' <ezeller@...>
Cc: aaa-dev@...
Subject: [SSL-RESTCONF] Query about etc/custom.properties

 

Hi Ryan / Evan / Ignacio,

 

I am able to make SSL-RESTCONF connection by modifying C:\master\distribution\karaf\target\assembly\etc\org.ops4j.pax.web as below:

 

org.osgi.service.http.secure.enabled=true

org.osgi.service.http.port.secure=8443

org.ops4j.pax.web.ssl.keystore=configuration/ssl/ctl.jks

org.ops4j.pax.web.ssl.truststore=configuration/ssl/truststore.jks

org.ops4j.pax.web.ssl.password=opendaylight

org.ops4j.pax.web.ssl.keypassword=opendaylight

 

I am just wondering if there is any way to make the same work with C:\master\distribution\karaf\target\assembly\etc\custom.properties without modifying org.ops4j.pax.web

 

Can you please help me out with this ?

 

Thanks,

Vamsi
Re: [SSL-RESTCONF] Query about etc/custom.properties

A Vamsikrishna
 

Hi Ryan / Evan / Ignacio,

 

I am able to make the SSL-RESTCONF work with custom.properties with the same changes I have put in org.ops4j.pax.web

 

That is:

 

org.osgi.service.http.secure.enabled=true

org.osgi.service.http.port.secure=8443

org.ops4j.pax.web.ssl.keystore=configuration/ssl/ctl.jks

org.ops4j.pax.web.ssl.truststore=configuration/ssl/truststore.jks

org.ops4j.pax.web.ssl.password=opendaylight

org.ops4j.pax.web.ssl.keypassword=opendaylight

 

org.ops4j.pax.web remains unchanged.

 

curl seems to be working fine:

 

stack@ubuntu:/etc/openvswitch$ curl -l http://192.168.56.1:8181/restconf/operational/network-topology:network-topology/ --user admin:admin

{"network-topology":{"topology":[{"topology-id":"flow:1"},{"topology-id":"ovsdb:1"},{"topology-id":"netvirt:1"},{"topology-id":"hwvtep:1"}]}}

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$ curl -l -k https://192.168.56.1:8443/restconf/operational/network-topology:network-topology/ --user admin:admin

{"network-topology":{"topology":[{"topology-id":"flow:1"},{"topology-id":"ovsdb:1"},{"topology-id":"netvirt:1"},{"topology-id":"hwvtep:1"}]}}

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

stack@ubuntu:/etc/openvswitch$

 

But if I try to open in browser I am seeing below errors:

 

 

 

Any idea how to fix this ??

 

Thanks,

Vamsi

 

 

From: A Vamsikrishna
Sent: Wednesday, January 31, 2018 3:55 PM
To: 'Ryan Goulding' <ryandgoulding@...>; 'Ignacio Dominguez Martinez-Casanueva' <i.dominguezm@...>; 'Evan Zeller' <ezeller@...>
Cc: aaa-dev@...
Subject: [SSL-RESTCONF] Query about etc/custom.properties

 

Hi Ryan / Evan / Ignacio,

 

I am able to make SSL-RESTCONF connection by modifying C:\master\distribution\karaf\target\assembly\etc\org.ops4j.pax.web as below:

 

org.osgi.service.http.secure.enabled=true

org.osgi.service.http.port.secure=8443

org.ops4j.pax.web.ssl.keystore=configuration/ssl/ctl.jks

org.ops4j.pax.web.ssl.truststore=configuration/ssl/truststore.jks

org.ops4j.pax.web.ssl.password=opendaylight

org.ops4j.pax.web.ssl.keypassword=opendaylight

 

I am just wondering if there is any way to make the same work with C:\master\distribution\karaf\target\assembly\etc\custom.properties without modifying org.ops4j.pax.web

 

Can you please help me out with this ?

 

Thanks,

Vamsi
[SSL-RESTCONF] Query about etc/custom.properties

A Vamsikrishna
 

Hi Ryan / Evan / Ignacio,

 

I am able to make SSL-RESTCONF connection by modifying C:\master\distribution\karaf\target\assembly\etc\org.ops4j.pax.web as below:

 

org.osgi.service.http.secure.enabled=true

org.osgi.service.http.port.secure=8443

org.ops4j.pax.web.ssl.keystore=configuration/ssl/ctl.jks

org.ops4j.pax.web.ssl.truststore=configuration/ssl/truststore.jks

org.ops4j.pax.web.ssl.password=opendaylight

org.ops4j.pax.web.ssl.keypassword=opendaylight

 

I am just wondering if there is any way to make the same work with C:\master\distribution\karaf\target\assembly\etc\custom.properties without modifying org.ops4j.pax.web

 

Can you please help me out with this ?

 

Thanks,

Vamsi
Re: [controller-dev] [Odlparent-dev] odlparent 3.0.2 for CONTROLLER-1799: Archetype self test during Maven build

Michael Vorburger <vorburger@...>
 

On Tue, Jan 23, 2018 at 4:51 PM, Ryan Goulding <ryandgoulding@...> wrote:
If you end up taking this on let me know, and I will abandon [0].  I had originally done this to avoid a ton of unused CLI related code in gen'd code.

Ryan, if by "you" you were talk to me ;) I'll clarify to avoid "developer deadlock" that my focus in the short term is in other areas than the archetype. So go for it! ;)
 

Regards,

Ryan Goulding

[0] https://git.opendaylight.org/gerrit/#/c/67070/

On Tue, Jan 23, 2018 at 10:45 AM, Michael Vorburger <vorburger@...> wrote:
On Tue, Jan 23, 2018 at 5:03 AM, Sam Hague <shague@...> wrote:
On Mon, Jan 22, 2018 at 9:30 PM, Tom Pantelis <tompantelis@...> wrote:
On Mon, Jan 22, 2018 at 9:26 PM, Michael Vorburger <vorburger@...> wrote:
On Mon, Jan 22, 2018 at 7:17 PM, Michael Vorburger <vorburger@...> wrote:
On Thu, Jan 18, 2018 at 5:25 PM, Tom Pantelis <tompantelis@...> wrote:
On Thu, Jan 18, 2018 at 10:45 AM, Michael Vorburger <vorburger@...> wrote:
On Wed, Nov 29, 2017 at 12:29 PM, Michael Vorburger <vorburger@...> wrote:
On Mon, Nov 27, 2017 at 8:10 PM, Michael Vorburger <vorburger@...> wrote:
Hello,

almost 3 months ago, on https://lists.opendaylight.org/pipermail/controller-dev/2017-September/013889.html, I had started a thread re. the mysterious problems hit in the controller archetype "self test", which occured on Gerrit and Jenkins, and only there (it worked locally even 3 months ago).

Today I finally made time to progress on this, and https://jira.opendaylight.org/browse/CONTROLLER-1799 has the write up what is going on there, documented for future reference.


Tx,
M.

PS: I'm hoping to work on https://jira.opendaylight.org/browse/INFRAUTILS-17 in the coming days, which will likely also require a change in odlparent; perhaps this and that could be pooled together into a 3.0.2 - anything else?

https://git.opendaylight.org/gerrit/#/c/66030/ and its related changes are what I meant here; if all of this, together with https://git.opendaylight.org/gerrit/#/c/65940/, could be released as an odlparent 3.0.2, in the hopefully not-too-distant future, that would be fabulous.

would any fellow controller commiter be willing to merge this https://git.opendaylight.org/gerrit/#/c/65941/ now? 

Tom, or even I volunteer to, then rebase https://git.opendaylight.org/gerrit/#/c/66545/ on top of that c/65941 and then I'm happy to merge that one after.

It would be good to get both of these archetype things into Oxygen still IMHO.

Agree - I rebased - will merge after

just done, but hit https://jira.opendaylight.org/browse/CONTROLLER-1810 .. following the Big Bump, the Archetype IT is actually broken.. seems to have something to do with some (shutdown related?) problem in AAA ? Don't be shy to comment on CONTROLLER-1810 if you have any clue what could be causing that. 

I'm hoping to merge https://git.opendaylight.org/gerrit/#/c/66545/ with that @Ignore ASAP anyway, if nobody has any objections; we can then subsquently remove the @Ignore in the archetype IT, when CONTROLLER-1810 is sorted.

FYI https://git.opendaylight.org/gerrit/#/c/66545/ is now finally merged, but without IT; in addition to https://jira.opendaylight.org/browse/CONTROLLER-1810 there seems to be a second (new?) problem with the IT of the archetype, detailed in https://jira.opendaylight.org/browse/CONTROLLER-1811.

What are people's views re. ditching the IT and/or CLI (suggested by Sam & Tom) from the archetype?

I think we should keep the startup archetype simple/basic and have an advanced archetype that has the extra fluff IT, CLI etc.
That's a good idea. This gets the basic users moving forward much easier. And if they really want something more than can run the advanced version.

That works for me too. Not ditch/remove the IT and/or CLI, but move into an "advanced" archetype. 

Because the current archetype is well known, let us keep that one as the existing basic one?

I wonder if we shold have a new "full" archetype, which would duplicate stuff from the basic (shame.. won't be keep consistent), or we could have something which augments / adds the IT and CLI to an existing basic archetype?

_______________________________________________
controller-dev mailing list
controller-dev@...ght.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev
Re: [controller-dev] [Odlparent-dev] odlparent 3.0.2 for CONTROLLER-1799: Archetype self test during Maven build

Ryan Goulding <ryandgoulding@...>
 

If you end up taking this on let me know, and I will abandon [0].  I had originally done this to avoid a ton of unused CLI related code in gen'd code.

Regards,

Ryan Goulding

[0] https://git.opendaylight.org/gerrit/#/c/67070/

On Tue, Jan 23, 2018 at 10:45 AM, Michael Vorburger <vorburger@...> wrote:
On Tue, Jan 23, 2018 at 5:03 AM, Sam Hague <shague@...> wrote:
On Mon, Jan 22, 2018 at 9:30 PM, Tom Pantelis <tompantelis@...> wrote:
On Mon, Jan 22, 2018 at 9:26 PM, Michael Vorburger <vorburger@...> wrote:
On Mon, Jan 22, 2018 at 7:17 PM, Michael Vorburger <vorburger@...> wrote:
On Thu, Jan 18, 2018 at 5:25 PM, Tom Pantelis <tompantelis@...> wrote:
On Thu, Jan 18, 2018 at 10:45 AM, Michael Vorburger <vorburger@...> wrote:
On Wed, Nov 29, 2017 at 12:29 PM, Michael Vorburger <vorburger@...> wrote:
On Mon, Nov 27, 2017 at 8:10 PM, Michael Vorburger <vorburger@...> wrote:
Hello,

almost 3 months ago, on https://lists.opendaylight.org/pipermail/controller-dev/2017-September/013889.html, I had started a thread re. the mysterious problems hit in the controller archetype "self test", which occured on Gerrit and Jenkins, and only there (it worked locally even 3 months ago).

Today I finally made time to progress on this, and https://jira.opendaylight.org/browse/CONTROLLER-1799 has the write up what is going on there, documented for future reference.


Tx,
M.

PS: I'm hoping to work on https://jira.opendaylight.org/browse/INFRAUTILS-17 in the coming days, which will likely also require a change in odlparent; perhaps this and that could be pooled together into a 3.0.2 - anything else?

https://git.opendaylight.org/gerrit/#/c/66030/ and its related changes are what I meant here; if all of this, together with https://git.opendaylight.org/gerrit/#/c/65940/, could be released as an odlparent 3.0.2, in the hopefully not-too-distant future, that would be fabulous.

would any fellow controller commiter be willing to merge this https://git.opendaylight.org/gerrit/#/c/65941/ now? 

Tom, or even I volunteer to, then rebase https://git.opendaylight.org/gerrit/#/c/66545/ on top of that c/65941 and then I'm happy to merge that one after.

It would be good to get both of these archetype things into Oxygen still IMHO.

Agree - I rebased - will merge after

just done, but hit https://jira.opendaylight.org/browse/CONTROLLER-1810 .. following the Big Bump, the Archetype IT is actually broken.. seems to have something to do with some (shutdown related?) problem in AAA ? Don't be shy to comment on CONTROLLER-1810 if you have any clue what could be causing that. 

I'm hoping to merge https://git.opendaylight.org/gerrit/#/c/66545/ with that @Ignore ASAP anyway, if nobody has any objections; we can then subsquently remove the @Ignore in the archetype IT, when CONTROLLER-1810 is sorted.

FYI https://git.opendaylight.org/gerrit/#/c/66545/ is now finally merged, but without IT; in addition to https://jira.opendaylight.org/browse/CONTROLLER-1810 there seems to be a second (new?) problem with the IT of the archetype, detailed in https://jira.opendaylight.org/browse/CONTROLLER-1811.

What are people's views re. ditching the IT and/or CLI (suggested by Sam & Tom) from the archetype?

I think we should keep the startup archetype simple/basic and have an advanced archetype that has the extra fluff IT, CLI etc.
That's a good idea. This gets the basic users moving forward much easier. And if they really want something more than can run the advanced version.

That works for me too. Not ditch/remove the IT and/or CLI, but move into an "advanced" archetype. 

Because the current archetype is well known, let us keep that one as the existing basic one?

I wonder if we shold have a new "full" archetype, which would duplicate stuff from the basic (shame.. won't be keep consistent), or we could have something which augments / adds the IT and CLI to an existing basic archetype?

_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev
Re: [Odlparent-dev] [controller-dev] odlparent 3.0.2 for CONTROLLER-1799: Archetype self test during Maven build

Michael Vorburger <vorburger@...>
 

On Tue, Jan 23, 2018 at 5:03 AM, Sam Hague <shague@...> wrote:
On Mon, Jan 22, 2018 at 9:30 PM, Tom Pantelis <tompantelis@...> wrote:
On Mon, Jan 22, 2018 at 9:26 PM, Michael Vorburger <vorburger@...> wrote:
On Mon, Jan 22, 2018 at 7:17 PM, Michael Vorburger <vorburger@...> wrote:
On Thu, Jan 18, 2018 at 5:25 PM, Tom Pantelis <tompantelis@...> wrote:
On Thu, Jan 18, 2018 at 10:45 AM, Michael Vorburger <vorburger@...> wrote:
On Wed, Nov 29, 2017 at 12:29 PM, Michael Vorburger <vorburger@...> wrote:
On Mon, Nov 27, 2017 at 8:10 PM, Michael Vorburger <vorburger@...> wrote:
Hello,

almost 3 months ago, on https://lists.opendaylight.org/pipermail/controller-dev/2017-September/013889.html, I had started a thread re. the mysterious problems hit in the controller archetype "self test", which occured on Gerrit and Jenkins, and only there (it worked locally even 3 months ago).

Today I finally made time to progress on this, and https://jira.opendaylight.org/browse/CONTROLLER-1799 has the write up what is going on there, documented for future reference.


Tx,
M.

PS: I'm hoping to work on https://jira.opendaylight.org/browse/INFRAUTILS-17 in the coming days, which will likely also require a change in odlparent; perhaps this and that could be pooled together into a 3.0.2 - anything else?

https://git.opendaylight.org/gerrit/#/c/66030/ and its related changes are what I meant here; if all of this, together with https://git.opendaylight.org/gerrit/#/c/65940/, could be released as an odlparent 3.0.2, in the hopefully not-too-distant future, that would be fabulous.

would any fellow controller commiter be willing to merge this https://git.opendaylight.org/gerrit/#/c/65941/ now? 

Tom, or even I volunteer to, then rebase https://git.opendaylight.org/gerrit/#/c/66545/ on top of that c/65941 and then I'm happy to merge that one after.

It would be good to get both of these archetype things into Oxygen still IMHO.

Agree - I rebased - will merge after

just done, but hit https://jira.opendaylight.org/browse/CONTROLLER-1810 .. following the Big Bump, the Archetype IT is actually broken.. seems to have something to do with some (shutdown related?) problem in AAA ? Don't be shy to comment on CONTROLLER-1810 if you have any clue what could be causing that. 

I'm hoping to merge https://git.opendaylight.org/gerrit/#/c/66545/ with that @Ignore ASAP anyway, if nobody has any objections; we can then subsquently remove the @Ignore in the archetype IT, when CONTROLLER-1810 is sorted.

FYI https://git.opendaylight.org/gerrit/#/c/66545/ is now finally merged, but without IT; in addition to https://jira.opendaylight.org/browse/CONTROLLER-1810 there seems to be a second (new?) problem with the IT of the archetype, detailed in https://jira.opendaylight.org/browse/CONTROLLER-1811.

What are people's views re. ditching the IT and/or CLI (suggested by Sam & Tom) from the archetype?

I think we should keep the startup archetype simple/basic and have an advanced archetype that has the extra fluff IT, CLI etc.
That's a good idea. This gets the basic users moving forward much easier. And if they really want something more than can run the advanced version.

That works for me too. Not ditch/remove the IT and/or CLI, but move into an "advanced" archetype. 

Because the current archetype is well known, let us keep that one as the existing basic one?

I wonder if we shold have a new "full" archetype, which would duplicate stuff from the basic (shame.. won't be keep consistent), or we could have something which augments / adds the IT and CLI to an existing basic archetype?
Re: [Odlparent-dev] [controller-dev] odlparent 3.0.2 for CONTROLLER-1799: Archetype self test during Maven build

Sam Hague <shague@...>
 



On Mon, Jan 22, 2018 at 9:30 PM, Tom Pantelis <tompantelis@...> wrote:


On Mon, Jan 22, 2018 at 9:26 PM, Michael Vorburger <vorburger@...> wrote:
On Mon, Jan 22, 2018 at 7:17 PM, Michael Vorburger <vorburger@...> wrote:
On Thu, Jan 18, 2018 at 5:25 PM, Tom Pantelis <tompantelis@...> wrote:
On Thu, Jan 18, 2018 at 10:45 AM, Michael Vorburger <vorburger@...> wrote:
On Wed, Nov 29, 2017 at 12:29 PM, Michael Vorburger <vorburger@...> wrote:
On Mon, Nov 27, 2017 at 8:10 PM, Michael Vorburger <vorburger@...> wrote:
Hello,

almost 3 months ago, on https://lists.opendaylight.org/pipermail/controller-dev/2017-September/013889.html, I had started a thread re. the mysterious problems hit in the controller archetype "self test", which occured on Gerrit and Jenkins, and only there (it worked locally even 3 months ago).

Today I finally made time to progress on this, and https://jira.opendaylight.org/browse/CONTROLLER-1799 has the write up what is going on there, documented for future reference.


Tx,
M.

PS: I'm hoping to work on https://jira.opendaylight.org/browse/INFRAUTILS-17 in the coming days, which will likely also require a change in odlparent; perhaps this and that could be pooled together into a 3.0.2 - anything else?

https://git.opendaylight.org/gerrit/#/c/66030/ and its related changes are what I meant here; if all of this, together with https://git.opendaylight.org/gerrit/#/c/65940/, could be released as an odlparent 3.0.2, in the hopefully not-too-distant future, that would be fabulous.

would any fellow controller commiter be willing to merge this https://git.opendaylight.org/gerrit/#/c/65941/ now? 

Tom, or even I volunteer to, then rebase https://git.opendaylight.org/gerrit/#/c/66545/ on top of that c/65941 and then I'm happy to merge that one after.

It would be good to get both of these archetype things into Oxygen still IMHO.

Agree - I rebased - will merge after

just done, but hit https://jira.opendaylight.org/browse/CONTROLLER-1810 .. following the Big Bump, the Archetype IT is actually broken.. seems to have something to do with some (shutdown related?) problem in AAA ? Don't be shy to comment on CONTROLLER-1810 if you have any clue what could be causing that. 

I'm hoping to merge https://git.opendaylight.org/gerrit/#/c/66545/ with that @Ignore ASAP anyway, if nobody has any objections; we can then subsquently remove the @Ignore in the archetype IT, when CONTROLLER-1810 is sorted.

FYI https://git.opendaylight.org/gerrit/#/c/66545/ is now finally merged, but without IT; in addition to https://jira.opendaylight.org/browse/CONTROLLER-1810 there seems to be a second (new?) problem with the IT of the archetype, detailed in https://jira.opendaylight.org/browse/CONTROLLER-1811.

What are people's views re. ditching the IT and/or CLI (suggested by Sam & Tom) from the archetype?

I think we should keep the startup archetype simple/basic and have an advanced archetype that has the extra fluff IT, CLI etc.
That's a good idea. This gets the basic users moving forward much easier. And if they really want something more than can run the advanced version.


_______________________________________________
Odlparent-dev mailing list
Odlparent-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/odlparent-dev
Re: [controller-dev] odlparent 3.0.2 for CONTROLLER-1799: Archetype self test during Maven build

Tom Pantelis
 



On Mon, Jan 22, 2018 at 9:26 PM, Michael Vorburger <vorburger@...> wrote:
On Mon, Jan 22, 2018 at 7:17 PM, Michael Vorburger <vorburger@...> wrote:
On Thu, Jan 18, 2018 at 5:25 PM, Tom Pantelis <tompantelis@...> wrote:
On Thu, Jan 18, 2018 at 10:45 AM, Michael Vorburger <vorburger@...> wrote:
On Wed, Nov 29, 2017 at 12:29 PM, Michael Vorburger <vorburger@...> wrote:
On Mon, Nov 27, 2017 at 8:10 PM, Michael Vorburger <vorburger@...> wrote:
Hello,

almost 3 months ago, on https://lists.opendaylight.org/pipermail/controller-dev/2017-September/013889.html, I had started a thread re. the mysterious problems hit in the controller archetype "self test", which occured on Gerrit and Jenkins, and only there (it worked locally even 3 months ago).

Today I finally made time to progress on this, and https://jira.opendaylight.org/browse/CONTROLLER-1799 has the write up what is going on there, documented for future reference.


Tx,
M.

PS: I'm hoping to work on https://jira.opendaylight.org/browse/INFRAUTILS-17 in the coming days, which will likely also require a change in odlparent; perhaps this and that could be pooled together into a 3.0.2 - anything else?

https://git.opendaylight.org/gerrit/#/c/66030/ and its related changes are what I meant here; if all of this, together with https://git.opendaylight.org/gerrit/#/c/65940/, could be released as an odlparent 3.0.2, in the hopefully not-too-distant future, that would be fabulous.

would any fellow controller commiter be willing to merge this https://git.opendaylight.org/gerrit/#/c/65941/ now? 

Tom, or even I volunteer to, then rebase https://git.opendaylight.org/gerrit/#/c/66545/ on top of that c/65941 and then I'm happy to merge that one after.

It would be good to get both of these archetype things into Oxygen still IMHO.

Agree - I rebased - will merge after

just done, but hit https://jira.opendaylight.org/browse/CONTROLLER-1810 .. following the Big Bump, the Archetype IT is actually broken.. seems to have something to do with some (shutdown related?) problem in AAA ? Don't be shy to comment on CONTROLLER-1810 if you have any clue what could be causing that. 

I'm hoping to merge https://git.opendaylight.org/gerrit/#/c/66545/ with that @Ignore ASAP anyway, if nobody has any objections; we can then subsquently remove the @Ignore in the archetype IT, when CONTROLLER-1810 is sorted.

FYI https://git.opendaylight.org/gerrit/#/c/66545/ is now finally merged, but without IT; in addition to https://jira.opendaylight.org/browse/CONTROLLER-1810 there seems to be a second (new?) problem with the IT of the archetype, detailed in https://jira.opendaylight.org/browse/CONTROLLER-1811.

What are people's views re. ditching the IT and/or CLI (suggested by Sam & Tom) from the archetype?

I think we should keep the startup archetype simple/basic and have an advanced archetype that has the extra fluff IT, CLI etc.
Re: [controller-dev] odlparent 3.0.2 for CONTROLLER-1799: Archetype self test during Maven build

Michael Vorburger <vorburger@...>
 

On Mon, Jan 22, 2018 at 7:17 PM, Michael Vorburger <vorburger@...> wrote:
On Thu, Jan 18, 2018 at 5:25 PM, Tom Pantelis <tompantelis@...> wrote:
On Thu, Jan 18, 2018 at 10:45 AM, Michael Vorburger <vorburger@...> wrote:
On Wed, Nov 29, 2017 at 12:29 PM, Michael Vorburger <vorburger@...> wrote:
On Mon, Nov 27, 2017 at 8:10 PM, Michael Vorburger <vorburger@...> wrote:
Hello,

almost 3 months ago, on https://lists.opendaylight.org/pipermail/controller-dev/2017-September/013889.html, I had started a thread re. the mysterious problems hit in the controller archetype "self test", which occured on Gerrit and Jenkins, and only there (it worked locally even 3 months ago).

Today I finally made time to progress on this, and https://jira.opendaylight.org/browse/CONTROLLER-1799 has the write up what is going on there, documented for future reference.


Tx,
M.

PS: I'm hoping to work on https://jira.opendaylight.org/browse/INFRAUTILS-17 in the coming days, which will likely also require a change in odlparent; perhaps this and that could be pooled together into a 3.0.2 - anything else?

https://git.opendaylight.org/gerrit/#/c/66030/ and its related changes are what I meant here; if all of this, together with https://git.opendaylight.org/gerrit/#/c/65940/, could be released as an odlparent 3.0.2, in the hopefully not-too-distant future, that would be fabulous.

would any fellow controller commiter be willing to merge this https://git.opendaylight.org/gerrit/#/c/65941/ now? 

Tom, or even I volunteer to, then rebase https://git.opendaylight.org/gerrit/#/c/66545/ on top of that c/65941 and then I'm happy to merge that one after.

It would be good to get both of these archetype things into Oxygen still IMHO.

Agree - I rebased - will merge after

just done, but hit https://jira.opendaylight.org/browse/CONTROLLER-1810 .. following the Big Bump, the Archetype IT is actually broken.. seems to have something to do with some (shutdown related?) problem in AAA ? Don't be shy to comment on CONTROLLER-1810 if you have any clue what could be causing that. 

I'm hoping to merge https://git.opendaylight.org/gerrit/#/c/66545/ with that @Ignore ASAP anyway, if nobody has any objections; we can then subsquently remove the @Ignore in the archetype IT, when CONTROLLER-1810 is sorted.

FYI https://git.opendaylight.org/gerrit/#/c/66545/ is now finally merged, but without IT; in addition to https://jira.opendaylight.org/browse/CONTROLLER-1810 there seems to be a second (new?) problem with the IT of the archetype, detailed in https://jira.opendaylight.org/browse/CONTROLLER-1811.

What are people's views re. ditching the IT and/or CLI (suggested by Sam & Tom) from the archetype?
Re: [netvirt-dev] Issues with odl-aaa-cli

Sam Hague <shague@...>
 

Patch below might also help Noel pushed this recently to fix issues with that shell command.

[1] https://git.opendaylight.org/gerrit/#/c/67353/

On Mon, Jan 22, 2018 at 2:16 PM, Michael Vorburger <vorburger@...> wrote:
Vamsi, and FYI JamO/Ryan/all interested:

On Mon, Jan 22, 2018 at 6:51 PM, Jamo Luhrsen <jluhrsen@...> wrote:
On 01/22/2018 01:43 AM, A Vamsikrishna wrote:
> Hi Ryan,
>
>  
>
> I am following below wiki to get the list of cipher suites supported by JVM:
>
>  
>
> http://docs.opendaylight.org/en/stable-carbon/user-guide/authentication-and-authorization-services.html#get-cipher-suites
>
>  
>
> opendaylight-user@root>
>
> opendaylight-user@root>feature:list -i | grep -i odl-aaa-cli
>
> odl-aaa-cli                                     | 0.7.0.SNAPSHOT   | x        | *Started* |
> odl-aaa-cli                                     | ODL :: aaa :: odl-aaa-cli
>
> opendaylight-user@root>
>
> opendaylight-user@root>
>
>  
>
> but when I give aaa: <tab> it’s throwing below error:
>
>  
>
> opendaylight-user@root>aaa:Error executing command: *Unable to find property descriptor rpcRegistry on class
> org.opendaylight.netvirt.neutronvpn.shell.ConfigureL3VpnComman*

interesting how it's throwing an error from some netvirt module (I've cc'd netvirt).

> opendaylight-user@root>
>
>  
>
> Any idea how to fix this error ?

Maybe you can file a Jira to start with?

yeah please raise a JIRA, but probably not in AAA but in either netvirt or perhaps even odlparent, or controller; I don't think this is aaa specific but a general problem with tab completion of either just that particular netvirt CLI command, or perhaps all/some of our shell commands? 

The "ComponentDefinitionException: Unable to find property descriptor rpcRegistry on class org.opendaylight.netvirt.neutronvpn.shell.ConfigureL3VpnCommand" thread on https://lists.opendaylight.org/pipermail/netvirt-dev/2017-December/thread.html already had something about this in December - and that was even before the big bump... Vamsi, do you want to re-read that thread, and ask your E// colleagues, if there was a solution?

Noel, this is also the same as what you already raised on https://lists.opendaylight.org/pipermail/netvirt-dev/2018-January/006127.html, isn't it? As I already suggested there, IMHO someone should try removing that availability="optional" there..


Thanks,
JamO


> I am using master branch.

Maybe this is something to do with the odlparent/yangtools version bump problems
we are dealing with?

Could be yet another impact of the Karaf upgrade in odlparent (similar to like that prompt stuff). Thank God we did this bump at the very beginning of a new major release, not after code freeze of the one we're hope to ship fairly soon... ;-) Although given thatit was already seen in December, may be in this particular case it's actually not even related. phew.

Tx,
M.
--
Michael Vorburger, Red Hat
vorburger@... | IRC: vorburger @freenode | ~ = http://vorburger.ch

 

Thanks,
JamO

> Thanks,
>
> Vamsi
>
>
>
> _______________________________________________
> aaa-dev mailing list
> aaa-dev@...
> https://lists.opendaylight.org/mailman/listinfo/aaa-dev
>
_______________________________________________
netvirt-dev mailing list
netvirt-dev@....org
https://lists.opendaylight.org/mailman/listinfo/netvirt-dev


_______________________________________________
netvirt-dev mailing list
netvirt-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/netvirt-dev
Re: [netvirt-dev] Issues with odl-aaa-cli

Michael Vorburger <vorburger@...>
 

Vamsi, and FYI JamO/Ryan/all interested:

On Mon, Jan 22, 2018 at 6:51 PM, Jamo Luhrsen <jluhrsen@...> wrote:
On 01/22/2018 01:43 AM, A Vamsikrishna wrote:
> Hi Ryan,
>
>  
>
> I am following below wiki to get the list of cipher suites supported by JVM:
>
>  
>
> http://docs.opendaylight.org/en/stable-carbon/user-guide/authentication-and-authorization-services.html#get-cipher-suites
>
>  
>
> opendaylight-user@root>
>
> opendaylight-user@root>feature:list -i | grep -i odl-aaa-cli
>
> odl-aaa-cli                                     | 0.7.0.SNAPSHOT   | x        | *Started* |
> odl-aaa-cli                                     | ODL :: aaa :: odl-aaa-cli
>
> opendaylight-user@root>
>
> opendaylight-user@root>
>
>  
>
> but when I give aaa: <tab> it’s throwing below error:
>
>  
>
> opendaylight-user@root>aaa:Error executing command: *Unable to find property descriptor rpcRegistry on class
> org.opendaylight.netvirt.neutronvpn.shell.ConfigureL3VpnComman*

interesting how it's throwing an error from some netvirt module (I've cc'd netvirt).

> opendaylight-user@root>
>
>  
>
> Any idea how to fix this error ?

Maybe you can file a Jira to start with?

yeah please raise a JIRA, but probably not in AAA but in either netvirt or perhaps even odlparent, or controller; I don't think this is aaa specific but a general problem with tab completion of either just that particular netvirt CLI command, or perhaps all/some of our shell commands? 

The "ComponentDefinitionException: Unable to find property descriptor rpcRegistry on class org.opendaylight.netvirt.neutronvpn.shell.ConfigureL3VpnCommand" thread on https://lists.opendaylight.org/pipermail/netvirt-dev/2017-December/thread.html already had something about this in December - and that was even before the big bump... Vamsi, do you want to re-read that thread, and ask your E// colleagues, if there was a solution?

Noel, this is also the same as what you already raised on https://lists.opendaylight.org/pipermail/netvirt-dev/2018-January/006127.html, isn't it? As I already suggested there, IMHO someone should try removing that availability="optional" there..


Thanks,
JamO


> I am using master branch.

Maybe this is something to do with the odlparent/yangtools version bump problems
we are dealing with?

Could be yet another impact of the Karaf upgrade in odlparent (similar to like that prompt stuff). Thank God we did this bump at the very beginning of a new major release, not after code freeze of the one we're hope to ship fairly soon... ;-) Although given thatit was already seen in December, may be in this particular case it's actually not even related. phew.

Tx,
M.
--
Michael Vorburger, Red Hat
vorburger@... | IRC: vorburger @freenode | ~ = http://vorburger.ch

 

Thanks,
JamO

> Thanks,
>
> Vamsi
>
>
>
> _______________________________________________
> aaa-dev mailing list
> aaa-dev@...
> https://lists.opendaylight.org/mailman/listinfo/aaa-dev
>
_______________________________________________
netvirt-dev mailing list
netvirt-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/netvirt-dev
Re: [controller-dev] odlparent 3.0.2 for CONTROLLER-1799: Archetype self test during Maven build

Michael Vorburger <vorburger@...>
 

On Thu, Jan 18, 2018 at 5:25 PM, Tom Pantelis <tompantelis@...> wrote:
On Thu, Jan 18, 2018 at 10:45 AM, Michael Vorburger <vorburger@...> wrote:
On Wed, Nov 29, 2017 at 12:29 PM, Michael Vorburger <vorburger@...> wrote:
On Mon, Nov 27, 2017 at 8:10 PM, Michael Vorburger <vorburger@...> wrote:
Hello,

almost 3 months ago, on https://lists.opendaylight.org/pipermail/controller-dev/2017-September/013889.html, I had started a thread re. the mysterious problems hit in the controller archetype "self test", which occured on Gerrit and Jenkins, and only there (it worked locally even 3 months ago).

Today I finally made time to progress on this, and https://jira.opendaylight.org/browse/CONTROLLER-1799 has the write up what is going on there, documented for future reference.


Tx,
M.

PS: I'm hoping to work on https://jira.opendaylight.org/browse/INFRAUTILS-17 in the coming days, which will likely also require a change in odlparent; perhaps this and that could be pooled together into a 3.0.2 - anything else?

https://git.opendaylight.org/gerrit/#/c/66030/ and its related changes are what I meant here; if all of this, together with https://git.opendaylight.org/gerrit/#/c/65940/, could be released as an odlparent 3.0.2, in the hopefully not-too-distant future, that would be fabulous.

would any fellow controller commiter be willing to merge this https://git.opendaylight.org/gerrit/#/c/65941/ now? 

Tom, or even I volunteer to, then rebase https://git.opendaylight.org/gerrit/#/c/66545/ on top of that c/65941 and then I'm happy to merge that one after.

It would be good to get both of these archetype things into Oxygen still IMHO.

Agree - I rebased - will merge after

just done, but hit https://jira.opendaylight.org/browse/CONTROLLER-1810 .. following the Big Bump, the Archetype IT is actually broken.. seems to have something to do with some (shutdown related?) problem in AAA ? Don't be shy to comment on CONTROLLER-1810 if you have any clue what could be causing that.

I'm hoping to merge https://git.opendaylight.org/gerrit/#/c/66545/ with that @Ignore ASAP anyway, if nobody has any objections; we can then subsquently remove the @Ignore in the archetype IT, when CONTROLLER-1810 is sorted.
  
 
--
Michael Vorburger, Red Hat
vorburger@... | IRC: vorburger @freenode | ~ = http://vorburger.ch


_______________________________________________
controller-dev mailing list
controller-dev@...ght.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev
Re: Issues with odl-aaa-cli

Jamo Luhrsen <jluhrsen@...>
 

On 01/22/2018 01:43 AM, A Vamsikrishna wrote:
Hi Ryan,

 

I am following below wiki to get the list of cipher suites supported by JVM:

 

http://docs.opendaylight.org/en/stable-carbon/user-guide/authentication-and-authorization-services.html#get-cipher-suites

 

opendaylight-user@root>

opendaylight-user@root>feature:list -i | grep -i odl-aaa-cli

odl-aaa-cli                                     | 0.7.0.SNAPSHOT   | x        | *Started* |
odl-aaa-cli                                     | ODL :: aaa :: odl-aaa-cli

opendaylight-user@root>

opendaylight-user@root>

 

but when I give aaa: <tab> it’s throwing below error:

 

opendaylight-user@root>aaa:Error executing command: *Unable to find property descriptor rpcRegistry on class
org.opendaylight.netvirt.neutronvpn.shell.ConfigureL3VpnComman*
interesting how it's throwing an error from some netvirt module (I've cc'd netvirt).

opendaylight-user@root>

 

Any idea how to fix this error ?
Maybe you can file a Jira to start with?

Thanks,
JamO


I am using master branch.
Maybe this is something to do with the odlparent/yangtools version bump problems
we are dealing with?

Thanks,
JamO

Thanks,

Vamsi



_______________________________________________
aaa-dev mailing list
aaa-dev@...
https://lists.opendaylight.org/mailman/listinfo/aaa-dev
Issues with odl-aaa-cli

A Vamsikrishna
 

Hi Ryan,

 

I am following below wiki to get the list of cipher suites supported by JVM:

 

http://docs.opendaylight.org/en/stable-carbon/user-guide/authentication-and-authorization-services.html#get-cipher-suites

 

opendaylight-user@root>

opendaylight-user@root>feature:list -i | grep -i odl-aaa-cli

odl-aaa-cli                                     | 0.7.0.SNAPSHOT   | x        | Started | odl-aaa-cli                                     | ODL :: aaa :: odl-aaa-cli

opendaylight-user@root>

opendaylight-user@root>

 

but when I give aaa: <tab> it’s throwing below error:

 

opendaylight-user@root>aaa:Error executing command: Unable to find property descriptor rpcRegistry on class org.opendaylight.netvirt.neutronvpn.shell.ConfigureL3VpnComman

 

opendaylight-user@root>

 

Any idea how to fix this error ?

 

I am using master branch.

 

Thanks,

Vamsi
Re: [Odlparent-dev] Jetty version problem in odlparent 3

Stephen Kitt <skitt@...>
 

On Fri, 19 Jan 2018 17:00:39 +0100
Stephen Kitt <skitt@...> wrote:
On Fri, 19 Jan 2018 16:55:52 +0100
Stephen Kitt <skitt@...> wrote:
On Fri, 19 Jan 2018 13:49:03 +0000
Martin Dindoffer <Martin.Dindoffer@...> wrote:
Seems like we should either patch jetty dependency back to 9.2.19
or make aaa/restconf behave nicely when updating jetty
underneath.
... or perhaps make SXP depend on pax-http-jetty instead; does that
work any better?
Or better yet, on odl-karaf-feat-jetty which is what ends up pulling
in pax-http-jetty, and which is what AAA uses.
On the AAA side of things, https://git.opendaylight.org/gerrit/67357
will help — it drops the explicit Jetty dependencies from the
odl-aaa-shiro feature.

Regards,

Stephen

?
application/pgp-signature

Re: aaa-cert-rpc 503 Service Unavailable

Ignacio Dominguez Martinez-Casanueva <i.dominguezm@...>
 

Hi Mohamed,

The suggested command returns the ODL certificate. Something strange is going on since I can perform the available operations in the RPC such as getODLCertificate or setNodeCertificate through the aaa CLI but not through the RESTCONF service.

Thank you very much,

Best regards,
Ignacio.

On 18.01.2018 16:19, Mohamed El-Serngawy wrote:
This not showing any helpful info. Would you try use the cli to make sure that the issue in aaa-cert service not restconf service

try below command let me know what is the output 

aaa:get-odl-cert -storepass <store_password>

On Thu, Jan 18, 2018 at 10:04 AM, Ignacio Dominguez Martinez-Casanueva <i.dominguezm@...> wrote:

Hi,

I configured full logging for AAA:

log:set TRACE org.opendaylight.aaa

When I send the REST request to /restconf/operations/aaa-cert-rpc:getNodeCertifcate, karaf.log just shows the following lines:

2018-01-18 15:55:02,603 | DEBUG | tp2130490805-969 | TokenAuthRealm                   | 261 - org.opendaylight.aaa.shiro - 0.5.2.Carbon | Authentication attempt using org.opendaylight.aaa.basic.HttpBasicAuth
2018-01-18 15:55:02,603 | DEBUG | tp2130490805-969 | TokenAuthRealm                   | 261 - org.opendaylight.aaa.shiro - 0.5.2.Carbon | Authentication attempt successful
2018-01-18 15:55:02,604 | DEBUG | tp2130490805-969 | AuthenticationListener           | 261 - org.opendaylight.aaa.shiro - 0.5.2.Carbon | Successful authentication attempt by admin from 138.150.194.90

Any suggestions for deeper debugging? I'm not sure if this could be related to the RPM release of Carbon SR2.

Thanks in advance,


Best regards,

Ignacio.
On 18.01.2018 15:51, Mohamed El-Serngawy wrote:
Hi,

Can you provide karaf logs, did u see any error messages?

BR

On Thu, Jan 18, 2018 at 9:46 AM, Ignacio Dominguez Martinez-Casanueva <i.dominguezm@...> wrote:

Hi Mohamed,

Yes, I changed it and now the first lines look as follows:

  ...
  <use-config>true</use-config>
  <use-mdsal>false</use-mdsal>
  ...

I have seen that after changing the <use-config> option to true, and restarting the opendaylight service, the two .jks files were created under configuration/ssl/. However, the issue with the RPC mechanism remains. Still getting 503 Unavailable.

Thanks in advance,


Best regards,

Ignacio.





On 18.01.2018 15:38, Mohamed El-Serngawy wrote:
Hi Ignacio,

Did you change the <use-config> to true.  The aaa-cert service config file under  etc/opendaylight/datastore/initial/config/aaa-cert-config.xml 

BR 

On Thu, Jan 18, 2018 at 5:17 AM, Ignacio Dominguez Martinez-Casanueva <i.dominguezm@...> wrote:

Hello,

I'm testing AAA project for Carbon SR2 (opendaylight-6.2.0-1.el7.rpm). I was working on the Certificate Management System in order to enable TLS/SSL for both RESTconf and OVS/OF communications, however, I spotted some strange behavior in this system.

After a fresh new installation of ODL, the "odl-aaa-cert" module should come installed by default according to this guide http://docs.opendaylight.org/en/stable-carbon/user-guide/authentication-and-authorization-services.html#id4. Indeed, such module is already installed but it seems the RPC mechanism is not available. When I try to retrieve ODL's certificate through /restconf/operations/aaa-cert-rpc:getODLCertificate I'm getting a 503 Service Unavailable response.

I also found that ctl.jks and truststore.jks files are not created under configuration/ssl/ folder after installing ODL. Is this behavior expected?

Thanks a lot for your help,


Best regards,

Ignacio.


_______________________________________________
aaa-dev mailing list
aaa-dev@...
https://lists.opendaylight.org/mailman/listinfo/aaa-dev
Re: aaa-cert-rpc 503 Service Unavailable

Mohamed ElSerngawy
 

This not showing any helpful info. Would you try use the cli to make sure that the issue in aaa-cert service not restconf service

try below command let me know what is the output 

aaa:get-odl-cert -storepass <store_password>

On Thu, Jan 18, 2018 at 10:04 AM, Ignacio Dominguez Martinez-Casanueva <i.dominguezm@...> wrote:

Hi,

I configured full logging for AAA:

log:set TRACE org.opendaylight.aaa

When I send the REST request to /restconf/operations/aaa-cert-rpc:getNodeCertifcate, karaf.log just shows the following lines:

2018-01-18 15:55:02,603 | DEBUG | tp2130490805-969 | TokenAuthRealm                   | 261 - org.opendaylight.aaa.shiro - 0.5.2.Carbon | Authentication attempt using org.opendaylight.aaa.basic.HttpBasicAuth
2018-01-18 15:55:02,603 | DEBUG | tp2130490805-969 | TokenAuthRealm                   | 261 - org.opendaylight.aaa.shiro - 0.5.2.Carbon | Authentication attempt successful
2018-01-18 15:55:02,604 | DEBUG | tp2130490805-969 | AuthenticationListener           | 261 - org.opendaylight.aaa.shiro - 0.5.2.Carbon | Successful authentication attempt by admin from 138.150.194.90

Any suggestions for deeper debugging? I'm not sure if this could be related to the RPM release of Carbon SR2.

Thanks in advance,


Best regards,

Ignacio.

On 18.01.2018 15:51, Mohamed El-Serngawy wrote:
Hi,

Can you provide karaf logs, did u see any error messages?

BR

On Thu, Jan 18, 2018 at 9:46 AM, Ignacio Dominguez Martinez-Casanueva <i.dominguezm@...> wrote:

Hi Mohamed,

Yes, I changed it and now the first lines look as follows:

  ...
  <use-config>true</use-config>
  <use-mdsal>false</use-mdsal>
  ...

I have seen that after changing the <use-config> option to true, and restarting the opendaylight service, the two .jks files were created under configuration/ssl/. However, the issue with the RPC mechanism remains. Still getting 503 Unavailable.

Thanks in advance,


Best regards,

Ignacio.





On 18.01.2018 15:38, Mohamed El-Serngawy wrote:
Hi Ignacio,

Did you change the <use-config> to true.  The aaa-cert service config file under  etc/opendaylight/datastore/initial/config/aaa-cert-config.xml 

BR 

On Thu, Jan 18, 2018 at 5:17 AM, Ignacio Dominguez Martinez-Casanueva <i.dominguezm@...> wrote:

Hello,

I'm testing AAA project for Carbon SR2 (opendaylight-6.2.0-1.el7.rpm). I was working on the Certificate Management System in order to enable TLS/SSL for both RESTconf and OVS/OF communications, however, I spotted some strange behavior in this system.

After a fresh new installation of ODL, the "odl-aaa-cert" module should come installed by default according to this guide http://docs.opendaylight.org/en/stable-carbon/user-guide/authentication-and-authorization-services.html#id4. Indeed, such module is already installed but it seems the RPC mechanism is not available. When I try to retrieve ODL's certificate through /restconf/operations/aaa-cert-rpc:getODLCertificate I'm getting a 503 Service Unavailable response.

I also found that ctl.jks and truststore.jks files are not created under configuration/ssl/ folder after installing ODL. Is this behavior expected?

Thanks a lot for your help,


Best regards,

Ignacio.


_______________________________________________
aaa-dev mailing list
aaa-dev@...
https://lists.opendaylight.org/mailman/listinfo/aaa-dev
221 - 240 of 1823