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

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

Hi Ignacio, I have installed Mdsal-apidocs feature but it’s showing as “Deploying” which ideally should be “Deployed”. opendaylight-user@root>feature:install

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.

Hi Ryan / Evan / Ignacio, I am able to make the SSL-RESTCONF work with custom.properties with the same changes I have put inorg.ops4j.pax.web That is:

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:

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! ;)

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]

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

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.

I think we should keep the startup archetype simple/basic and have an advanced archetype that has the extra fluff IT, CLI etc.

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

Patch below might also help Noel pushed this recently to fix issues with that shell command. [1] https://git.opendaylight.org/gerrit/#/c/67353/

Vamsi, and FYI JamO/Ryan/all interested: 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

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?)

interesting how it's throwing an error from some netvirt module (I've cc'd netvirt). Maybe you can file a Jira to start with? Thanks, JamO Maybe this is something to do with the

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

Stephen Kitt <skitt@...> wrote: 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

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

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