[Crowbar] postgresql support
Gregory_Althaus at Dell.com
Gregory_Althaus at Dell.com
Wed Mar 28 09:38:09 CDT 2012
Yes - this is cool. Matt Ray keeps mentioning this to me. The trick will be creating this and integrating it with our barclamps.
Actually, this raises a different problem though. The database cookbook has more and specific functionality than we may want. Also, the current barclamps allow some dependence separation that the database cookbook doesn't. I need to think about this some more.
From: crowbar-bounces On Behalf Of Haselwanter Edmund
Sent: Wednesday, March 28, 2012 9:29 AM
To: Ralf Haferkamp
Subject: Re: [Crowbar] postgresql support
IMHO if you try to change this I would love to see
were you can hide implementation details
# do the same but pass the provider to the database resource database_user 'disenfranchised' do
so you could configure the provider and connection to use but keep the stuff in the keystone/glance etc. stable
On Mar 28, 2012, at 4:12 PM, Ralf Haferkamp wrote:
> I am currently trying to figure out ways for adding support to deploy
> openstack with PostgreSQL used as the database for keystone, glance etc.
> For that I created a basic PostgreSQL barclamp (based on the
> postgresql cookbook in https://github.com/opscode/cookbooks).
> However, I'd like to avoid bloating the barclamps that currently use
> the mysql_database chef-resource for e.g. creating databases (such as
> keystone, glance, nove and dashboard) with too many
> if node[:keystone][:sql_engine] == "postgresql"
> branches to call the new postgresql_database chef-resource I created.
> One way to achieve that seems to be to create a new resource say
> "openstack_database" that provides the needed actions (e.g. create_db,
> create_user) and create two separate providers for that resource
> (openstack_postgresqldb and openstack_mysqldb), which would just map
> to the specific resources from the mysql and postgresql cookbooks.
> That way it should be possible to make large parts of the current
> mysql specific code independent of the actually used database
> implementation by replacing the mysql_database invocations with calls
> to openstack_database (+ setting the "provider" attribute to the
> correct implementation). Does that make sense? Are there better ways to achieve this?
> Crowbar mailing list
> Crowbar at dell.com
> For more information: https://github.com/dellcloudedge/crowbar/wiki
DI Edmund Haselwanter, edmund at haselwanter.com, http://edmund.haselwanter.com/ http://www.iteh.at | http://facebook.com/iTeh.solutions | http://at.linkedin.com/in/haselwanteredmund
Crowbar mailing list
Crowbar at dell.com
For more information: https://github.com/dellcloudedge/crowbar/wiki
More information about the Crowbar