[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: cartridge user dependencies in own package



To date, if an OpenShift Online user wanted additional libraries and they were popular. We just added the dependency to the cartridge spec file.  In a one product world it was simple and easy.

/jwh


----- Original Message -----
> From: "Ben Parees" <bparees redhat com>
> To: "Troy Dawson" <tdawson redhat com>
> Cc: dev lists openshift redhat com
> Sent: Friday, November 22, 2013 2:39:54 PM
> Subject: Re: cartridge user dependencies in own package
> 
> Being new to the team, I could use some background on why the cartridges
> currently *do* have those dependencies...  and what will it mean for a
> deployment if the "extra" things are not there?
> 
> eg why is rpm-build a dependency for the perl cartridge?  is it really so I
> can deploy a perl app that builds packages, or is it needed by some aspect
> of the OS infrastructure code?
> 
> 
> Ben Parees | OpenShift
> 
> ----- Original Message -----
> From: "Troy Dawson" <tdawson redhat com>
> To: dev lists openshift redhat com
> Sent: Friday, November 22, 2013 4:12:43 PM
> Subject: cartridge user dependencies in own package
> 
> Hello,
> For those that don't know, we currently have alot of what I call "user
> dependencies" in our openshift-origin-cartridge rpm packages.
> I will use openshift-origin-cartridge-perl as my example.
> In order to install the ropenshift-origin-cartridge-perl pm you have to have
> 
> httpd facter rubygem(openshift-origin-node)
> openshift-origin-node-util mod_perl
> perl-DBD-SQLite perl-DBD-MySQL perl-MongoDB ImageMagick-perl
> gd-devel perl-App-cpanminus perl-CPAN perl-CPANPLUS
> db4-devel rpm-build expat-devel perl-IO-Socket-SSL gdbm-devel
> 
> As you start reading through that requirement list you think to
> yourself, "well of course it need those" ...
> then you get to the Database entries and you think ... "Well, that makes
> sense"
> then you read some of the others and think ... "If you say so, I guess
> we need them"
> and then you read rpm-build and think ...  "What??  why does my perl
> cartridge need to build rpm's"
> 
> I'd like to work on a change, and make a proposal.
> 
> Let's change the requirements of the cartridges to only require what is
> needed to make the cartridge run.
> All the other requirements, let's put into their own requirements rpm.
> 
> * openshift-origin-cartridge-perl
>     requires:
>      rubygem(openshift-origin-node)
>      openshift-origin-node-util
>      mod_perl
>      perl-App-cpanminus
> 
> * openshift-origin-cartridge-perl-users
>     requires:
>      openshift-origin-cartridge-perl
>      perl-DBD-SQLite
>      perl-DBD-MySQL
>      perl-MongoDB
>      ImageMagick-perl
>      ...etc...
> 
> I don't want to do this until release 3 is done.  But I'd like to get
> the groud work started for the change.  There are a couple things that
> need to be decided.
> 
> 1 - Should we do this?
> 
> 2 - What would we call the new rpms?
> -- openshift-origin-cartridge-<cart>-users ?
> -- openshift-origin-cart-dep-<cart> ?
> 
> 3 - Do we have just one big dependency rpm per cart, or should we have
> several?
> -- openshift-origin-app-dep-redmine ?
> -- openshift-origin-lang-dep-ta-lib ?
> 
> Thoughts
> Troy
> 
> _______________________________________________
> dev mailing list
> dev lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> 
> _______________________________________________
> dev mailing list
> dev lists openshift redhat com
> http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
> 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]