[controller-dev] Need OVA image used in BGP & PCEP Tutorial

2016-12-09 Thread Sonu Gupta
HI Ajay,

This is Sonu Gupta started working in ODL as a software developer.
First of all thanks for the BGP & PCEP Tutorial with set-up demo.
I am following the below link for demo tutorial

https://www.youtube.com/watch?v=B4SZW2a-CrM&feature=youtu.be&list=PL8F5jrwEpGAjOD5jw6iVOWUqsiqQRtPmw

It will be very helpful if you can please share me the OVA file used for
this set-up.

Thanks
Sonu Gupta
___
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev


[controller-dev] Help needed for the Karaf 4 upgrade

2016-12-09 Thread Stephen Kitt
Hi,

I'm having a hard time verifying the features in controller, in
particular features-mdsal which is failing in odd ways. I'd greatly
appreciate help figuring out what's going wrong!

To reproduce:

* build odlparent with https://git.opendaylight.org/gerrit/49155
* build yangtools and mdsal
* build controller with https://git.opendaylight.org/gerrit/26161

This will blow up at features-mdsal (so at least all the config
features now work). As usual -Dkaraf.keep.unpack will leave the Pax
Exam Karaf distributions around in target/pax so you can run Karaf
manually and poke around.

Thanks,

Stephen


pgpRQWsN5yx51.pgp
Description: OpenPGP digital signature
___
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev


[controller-dev] FW: IncorrectNestingException while trying to write augmented instructions

2016-12-09 Thread Faseela K
 Hi ,
  We have been stuck with an exception for so long, not knowing how to fix.

 We have a container which uses opendaylight-flow-types:instruction-list[0]

 Whenever we try to populate this list with an instruction which is augmented 
from the base[1], it is throwing the below error, any pointers?

  org.opendaylight.yangtools.binding.data.codec.impl.IncorrectNestingException: 
Supplied class interface 
org.opendaylight.yang.gen.v1.urn.opendaylight.openflowplugin.extension.nicira.action.rev140714.nodes.node.table.flow.instructions.instruction.instruction.apply.actions._case.apply.actions.action.action.NxActionRegLoadNodesNodeTableFlowApplyActionsCase
 is not valid case^M
at 
org.opendaylight.yangtools.binding.data.codec.impl.IncorrectNestingException.create(IncorrectNestingException.java:28)^M
at 
org.opendaylight.yangtools.binding.data.codec.impl.DataContainerCodecContext.childNonNull(DataContainerCodecContext.java:180)[92:org.opendaylight.mdsal.binding-dom-codec:0.9.2.SNAPSHOT]^M
at 
org.opendaylight.yangtools.binding.data.codec.impl.ChoiceNodeCodecContext.streamChild(ChoiceNodeCodecContext.java:110)[92:org.opendaylight.mdsal.binding-dom-codec:0.9.2.SNAPSHOT]^M
at 
org.opendaylight.yangtools.binding.data.codec.impl.BindingToNormalizedStreamWriter.enter(BindingToNormalizedStreamWriter.java:74)[92:org.opendaylight.mdsal.binding-dom-codec:0.9.2.SNAPSHOT]^M
at 
org.opendaylight.yangtools.binding.data.codec.impl.BindingToNormalizedStreamWriter.startCase(BindingToNormalizedStreamWriter.java:144)[92:org.opendaylight.mdsal.binding-dom-codec:0.9.2.SNAPSHOT]^M
at 
org.opendaylight.yang.gen.v1.urn.opendaylight.openflowplugin.extension.nicira.action.rev140714.nodes.node.table.flow.instructions.instruction.instruction.apply.actions._case.apply.actions.action.action.NxActionRegLoadNodesNodeTableFlowApplyActionsCase$StreamWriter.serialize(DataObjectSerializerPrototype.java)[276:org.opendaylight.openflowplugin.extension-nicira:0.3.2.SNAPSHOT]^M
at 
org.opendaylight.yangtools.binding.data.codec.impl.BindingNormalizedNodeCodecRegistry$DataObjectSerializerProxy.serialize(BindingNormalizedNodeCodecRegistry.java:295)[92:org.opendaylight.mdsal.binding-dom-codec:0.9.2.SNAPSHOT]^M
at 
org.opendaylight.yangtools.binding.data.codec.util.ChoiceDispatchSerializer.serialize(ChoiceDispatchSerializer.java:47)[92:org.opendaylight.mdsal.binding-dom-codec:0.9.2.SNAPSHOT]^M
at 
org.opendaylight.yang.gen.v1.urn.opendaylight.action.types.rev131112.action.list.Action$StreamWriter.serialize(DataObjectSerializerPrototype.java)[259:org.opendaylight.openflowplugin.model.flow-base:0.3.2.SNAPSHOT]^M
at 
org.opendaylight.yang.gen.v1.urn.opendaylight.flow.types.rev131026.instruction.instruction.apply.actions._case.ApplyActions$StreamWriter.serialize(DataObjectSerializerPrototype.java)[259:org.opendaylight.openflowplugin.model.flow-base:0.3.2.SNAPSHOT]^M
at 
org.opendaylight.yang.gen.v1.urn.opendaylight.flow.types.rev131026.instruction.instruction.ApplyActionsCase$StreamWriter.serialize(DataObjectSerializerPrototype.java)[259:org.opendaylight.openflowplugin.model.flow-base:0.3.2.SNAPSHOT]^M
at 
org.opendaylight.yangtools.binding.data.codec.impl.BindingNormalizedNodeCodecRegistry$DataObjectSerializerProxy.serialize(BindingNormalizedNodeCodecRegistry.java:295)[92:org.opendaylight.mdsal.binding-dom-codec:0.9.2.SNAPSHOT]^M
at 
org.opendaylight.yangtools.binding.data.codec.util.ChoiceDispatchSerializer.serialize(ChoiceDispatchSerializer.java:47)[92:org.opendaylight.mdsal.binding-dom-codec:0.9.2.SNAPSHOT]^M
at 
org.opendaylight.yang.gen.v1.urn.opendaylight.flow.types.rev131026.instruction.list.Instruction$StreamWriter.serialize(DataObjectSerializerPrototype.java)[259:org.opendaylight.openflowplugin.model.flow-base:0.3.2.SNAPSHOT]^M
at 
org.opendaylight.yang.gen.v1.urn.opendaylight.genius.interfacemanager.servicebinding.rev160406.StypeOpenflow$StreamWriter.serialize(DataObjectSerializerPrototype.java)[286:org.opendaylight.genius.interfacemanager-api:0.1.2.SNAPSHOT]^M
at 
org.opendaylight.yangtools.binding.data.codec.impl.BindingNormalizedNodeCodecRegistry$DataObjectSerializerProxy.serialize(BindingNormalizedNodeCodecRegistry.java:295)[92:org.opendaylight.mdsal.binding-dom-codec:0.9.2.SNAPSHOT]^M
at 
org.opendaylight.yangtools.binding.data.codec.util.AugmentableDispatchSerializer.emitAugmentation(AugmentableDispatchSerializer.java:79)[92:org.opendaylight.mdsal.binding-dom-codec:0.9.2.SNAPSHOT]^M
at 
org.opendaylight.yangtools.binding.data.codec.util.AugmentableDispatchSerializer.serialize(AugmentableDispatchSerializer.java:51)[92:org.opendaylight.mdsal.binding-dom-codec:0.9.2.SNAPSHOT]^M
at 
org.opendaylight.yang.gen.v1.urn.opendaylight.genius.interfacemanager.servicebinding.rev160406.service.bindings.services.info.BoundServices$StreamWriter.serialize(DataObjectSerializerPrototype.java)[286:org.opendaylig

Re: [controller-dev] Need OVA image used in BGP & PCEP Tutorial

2016-12-09 Thread Alexis de Talhouƫt
Sonu,

You should find what you're after here: 
https://wiki.opendaylight.org/view/OpenDaylight_Presentations:Main#OpenDaylight_Summit_Seattle
 


Alexis

> On Dec 9, 2016, at 4:47 AM, Sonu Gupta  wrote:
> 
> HI Ajay,
> 
> This is Sonu Gupta started working in ODL as a software developer.
> First of all thanks for the BGP & PCEP Tutorial with set-up demo.
> I am following the below link for demo tutorial
> 
> https://www.youtube.com/watch?v=B4SZW2a-CrM&feature=youtu.be&list=PL8F5jrwEpGAjOD5jw6iVOWUqsiqQRtPmw
>  
> 
> 
> It will be very helpful if you can please share me the OVA file used for this 
> set-up.
> 
> Thanks
> Sonu Gupta 
> ___
> controller-dev mailing list
> controller-dev@lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/controller-dev

___
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev


Re: [controller-dev] [Odlparent-dev] Question about opendaylight-karaf-empty

2016-12-09 Thread Vratko Polak -X (vrpolak - PANTHEON TECHNOLOGIES at Cisco)
I got an idea for a workaround, just use
previously released version of opendaylight-karaf-empty
for SingleFeaturetest only, and hope the results are valid.
https://git.opendaylight.org/gerrit/49188
See comments in pom.xml file.

As usual, no time to test that myself,
feel free to test and improve.

Vratko.

-Original Message-
From: odlparent-dev-boun...@lists.opendaylight.org 
[mailto:odlparent-dev-boun...@lists.opendaylight.org] On Behalf Of Robert Varga
Sent: 5 December, 2016 17:22
To: Michael Vorburger ; Ryan Goulding 

Cc: controller-dev ; 
odlparent-...@lists.opendaylight.org
Subject: Re: [Odlparent-dev] [controller-dev] Question about 
opendaylight-karaf-empty

On 12/05/2016 05:11 PM, Robert Varga wrote:
> On 12/05/2016 04:55 PM, Michael Vorburger wrote:
>>
>> The thing is, opendaylight-karaf-empty zip is actually ~112 MB. 
>> This file is downloaded whenever we perform a singleFeatureTest (to
>> my understanding), which probably puts a lot of stress on nexus,
>> especially when not all the features are necessarily needed.  Is
>> this something we could disable and allow singleFeatureTest to run
>> in a non-offline mode?  I am not quite sure the implications of
>> doing so, and that is why I decided to pose the question to these
>> mailing lists.
>>
>>
>> did you ever get any replies to this? I had raised a similar Q in 
>> "Move opendaylight-karaf-empty (and opendaylight-karaf-resources) to 
>> fixed version", although I came at it from another angle - I'm 
>> questioning why opendaylight-karaf-empty has to be a daily SNAPSHOT, 
>> and suggested to do something about that.. let me bump that thread and add 
>> you directly.
> 
> The answer to this ... depends. karaf-empty is pulling in our 
> branding, which may be something which changes during a release.
> 
> I think this would be doable if we had a karaf-packaging base project, 
> which would release on its own and would then be pulled into odlparent
> -- that would achieve this without going for all of the version skew 
> induced by having an odlparent version bump going on...

To add further details to this, to cover the 'snapshot download' question.

This stems from how our Jenkins and Nexus are configured -- -merge jobs cannot 
publish to -release repo, that is something only -release jobs can do.

This is not something we want to change, as all of .m2/repository assumes that 
released artifacts do not ever change, hence you need to make sure you record 
the release in SCM.

Before anyone suggests it: performing 'partial' project releases is technically 
possible, but a sure way to wreck something down the line (developer sanity 
being one of the more obvious candidates).

Regards,
Robert

___
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev