cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pradeep Cloudstack <pradeepcloudst...@yahoo.com.INVALID>
Subject Re: CS 4.3 - Registering network-element plugin
Date Tue, 24 Jun 2014 11:23:06 GMT
Hi Punith,
we will have this file under /etc/cloudstack/management
Customer can also edit this file


-Pradeep



________________________________
 From: Punith S <punith.s@cloudbyte.com>
To: cloudstack <dev@cloudstack.apache.org>; Pradeep Cloudstack <pradeepcloudstack@yahoo.com>

Sent: Tuesday, June 24, 2014 4:08 PM
Subject: Re: CS 4.3 - Registering network-element plugin
 

hi pradeep,

you can put your custom key value pairs in your *-context.xml inside your
bean

for example
<bean id="elastistorDataStoreProvider"

class="org.apache.cloudstack.storage.datastore.provider.ElastistorPrimaryDataStoreProvider">
        <property name="esmanagementip" value="10.10.171.180"/>
        <property name="esapikey"
value="PubSInZaCji8hrRfOsCxgbug2I2k_sRJ0i2a9qmAzZIiCTcFPmZelzx6uNK9TYgqkdohCmq1L2J9eYmUe9YO6A"/>
        <property name="esaccountid"
value="9e9f67d5-e06f-4d63-a0b8-e7255cba84b8"/>
        <property name="espoolid"
value="d2d15d11-0f06-3426-a097-3e6e8b36f85c"/>
        <property name="esdefaultgateway" value="10.10.1.1"/>
        <property name="essubnet" value="8"/>
        <property name="estntinterface" value="em0"/>
  </bean>

also i'm curious to know how to move these properties out of the jar ?, can
you please elaborate.

thanks.



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

> Hi Punith,
> yes; the properties file contains custom key value pairs
>
> We have decided move this file out of our jar. So, no issues now
>
> -Pradeep
>
>
>
> ________________________________
>  From: Punith S <punith.s@cloudbyte.com>
> To: cloudstack <dev@cloudstack.apache.org>; Pradeep Cloudstack <
> pradeepcloudstack@yahoo.com>
> Sent: Tuesday, June 24, 2014 3:52 PM
> Subject: Re: CS 4.3 - Registering network-element plugin
>
>
> 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
>



-- 
regards,

punith s
cloudbyte.com
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message