cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Punith S <punit...@cloudbyte.com>
Subject Re: CS 4.3 - Registering network-element plugin
Date Tue, 24 Jun 2014 10:22:39 GMT
hi pradeep,

does the JuniperNetworkGuru.properties file contain your custom key value
pairs to be used in the plugin ?

thanks.


On Tue, Jun 24, 2014 at 2:56 PM, Pradeep Cloudstack <
pradeepcloudstack@yahoo.com.invalid> wrote:

> Hi Punith,
> the war contains the jar file. Also, the names are correct.
>
> In out network-element pom.xml file, we had made entries to ensure that a
> property file
> is bundled with the jar
>
> ***********************************************************
>   <build>
>      <resources>
>        <resource>
>          <directory>src</directory>
>          <filtering>false</filtering>
>          <includes>
>                  <include>JuniperNetworkGuru.properties</include>
>              </includes>
>        </resource>
>      </resources>
>    </build>
> ***********************************************************
>
> This seems to be causing the issue. If I remove this entry, I see that the
> spring.xml and module.properties
> are bundled in the jar, but our JuniperNetworkGuru.properties will not get
> bundled
>
> -Pradeep
>
>
>
> ________________________________
>  From: Punith S <punith.s@cloudbyte.com>
> To: cloudstack <dev@cloudstack.apache.org>; Pradeep Cloudstack <
> pradeepcloudstack@yahoo.com>
> Sent: Tuesday, June 24, 2014 12:55 PM
> Subject: Re: CS 4.3 - Registering network-element plugin
>
>
> hi pradeep,
>
> can you make sure your jar is present in the cloud war.
> to make this happen you have to register the dependency in the client
> pom.xml file.
>
> also you need to register your plugin in the plugin pom.xml file and make
> sure the provider name matches.
>
> thanks.
>
>
>
> On Tue, Jun 24, 2014 at 12:38 PM, Pradeep Cloudstack <
> pradeepcloudstack@yahoo.com.invalid> wrote:
>
> > Thanks Punith.
> > We had tried this.
> > However the jar file that is built didnot include the
> spring-*-context.xml
> > and module.properties
> > as a result of which our plugin didnot get registered.
> >
> > We followed the approach that was taken for vxlan and created artifacts
> on
> > similar lines.
> >
> > Can you pls help on what we are missing ?
> >
> >
> > -Pradeep
> >
> >
> >
> > ________________________________
> >  From: Punith S <punith.s@cloudbyte.com>
> > To: cloudstack <dev@cloudstack.apache.org>; Pradeep Cloudstack <
> > pradeepcloudstack@yahoo.com>
> > Sent: Tuesday, June 24, 2014 12:11 PM
> > Subject: Re: CS 4.3 - Registering network-element plugin
> >
> >
> > hi pradeep,
> >
> > the spring framework has been modularized in 4.3 onwards,
> > this link might help you in registering the new plugin.
> >
> >
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Plug-ins%2C+Modules%2C+and+Extensions
> >
> > thanks,
> >
> >
> >
> >
> >
> > On Tue, Jun 24, 2014 at 11:57 AM, Pradeep Cloudstack <
> > pradeepcloudstack@yahoo.com.invalid> wrote:
> >
> > > Hi team,
> > > I need some help in registering network-element plugin in a 4.3
> > > installation.
> > >
> > > In 4.2 release, we used to make entries in componentContext.xml.
> > >
> > > However in 4.3, looks like there is a NetworkGuru Registry.
> > > How do we register our plugin here?
> > >
> > > -Pradeep
> > >
> >
> >
> >
> > --
> > regards,
>
> >
> > punith s
> > cloudbyte.com
> >
>
>
>
> --
> regards,
>
> punith s
> cloudbyte.com
>



-- 
regards,

punith s
cloudbyte.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message