[Crowbar] few more merges into pebbles

[Arkady_Kanevsky]

The following PRs have been merged into pebbles:
https://github.com/crowbar/barclamp-tempest/pull/47
https://github.com/crowbar/barclamp-tempest/pull/47

Will generate cherry picked PRs against Roxy today.
Thanks,
Arkady

[cid:image001.jpg@01CEBE91.CC8581C0]


Arkady Kanevsky, Ph.D.

Director of SW Development

Enterprise Solution Group

+1 512 723 5264 | arkady_kanev...@dell.com



<>___
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/

[Crowbar] Wrapping upstream stackforge cookbooks (proof of concept)

[Ionuț Arțăriși]

Hello,

I started working on a proof of concept to see if we could wrap the 
upstream stackforge cookbooks[1] in the existing barclamps.

The stackforge cookbooks support the grizzly openstack branch. There are 
several advantages to using them: the style of the cookbooks is clearer 
and more orthogonal (e.g. platform-specific things are set in the 
attributes file), they have good chefspec test coverage and a growing 
community.

I have a first working version up in a new branch in our SUSE-Cloud 
keystone-barclamp repository[2]. Some pieces aren't there yet, like 
password management and SSL support, but it works successfully with the 
other openstack barclamps in the release/pebbles/master branch.

The code is pretty simple, it basically just maps some of the existing 
attributes from crowbar-names to stackforge-names. Basically all of it 
is in the default recipe[3]. I haven't changed any existing attribute 
names; changing those could reduce the size of the default recipe.

So like I said, this is just a working proof of concept which we'd like 
to get some feedback on from the wider crowbar community to see if this 
would be a worthwhile path to follow.

Thank you,
Ionuț

[1] https://launchpad.net/openstack-chef
[2] https://github.com/SUSE-Cloud/barclamp-keystone/tree/stackforge-wrap
[3] 
https://github.com/SUSE-Cloud/barclamp-keystone/blob/stackforge-wrap/chef/cookbooks/keystone/recipes/default.rb
 

___
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/

Re: [Crowbar] Wrapping upstream stackforge cookbooks (proof of concept)

[Rob_Hirschfeld]

Ionut,
One of the major objectives for CB2 work has been to embrace the attribute 
injection style of cookbook so that we can align with Stackforge.
Rob

-Original Message-
From: crowbar-bounces On Behalf Of Ionu? Ar?ari?i
Sent: Tuesday, October 01, 2013 11:11 AM
To: crowbar
Subject: [Crowbar] Wrapping upstream stackforge cookbooks (proof of concept)

Hello,

I started working on a proof of concept to see if we could wrap the upstream 
stackforge cookbooks[1] in the existing barclamps.

The stackforge cookbooks support the grizzly openstack branch. There are 
several advantages to using them: the style of the cookbooks is clearer and 
more orthogonal (e.g. platform-specific things are set in the attributes file), 
they have good chefspec test coverage and a growing community.

I have a first working version up in a new branch in our SUSE-Cloud 
keystone-barclamp repository[2]. Some pieces aren't there yet, like password 
management and SSL support, but it works successfully with the other openstack 
barclamps in the release/pebbles/master branch.

The code is pretty simple, it basically just maps some of the existing 
attributes from crowbar-names to stackforge-names. Basically all of it is in 
the default recipe[3]. I haven't changed any existing attribute names; changing 
those could reduce the size of the default recipe.

So like I said, this is just a working proof of concept which we'd like to get 
some feedback on from the wider crowbar community to see if this would be a 
worthwhile path to follow.

Thank you,
Ionuț

[1] https://launchpad.net/openstack-chef
[2] https://github.com/SUSE-Cloud/barclamp-keystone/tree/stackforge-wrap
[3]
https://github.com/SUSE-Cloud/barclamp-keystone/blob/stackforge-wrap/chef/cookbooks/keystone/recipes/default.rb

___
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/
___
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/

Re: [Crowbar] mesa-1.6 - cinder barclamp fails when applying proposal

[Simon_Jakesch]

Daniel,

we've taken a look at your issue, and we're having a hard time coming up with a 
path on how you got to where you are now. Specifically your second statement 
about being able to login with the cinder.conf password. None the less here are 
the things you can do to either fix this issues or provide more information to 
use:

We can try to recreate the cinder DB and reinitialize the password. In order to 
do so we recommend you stop chef-client from running on whichever node you have 
the DB located (which is typically the node that runs all the other MySQL DBs). 
Then you should drop the DB via the usual mysqladmin command. After we upload 
the whole Barclamp, this will reset all the associated Databags on the chef 
server, which is exactly what you want. You do this via: 
/opt/dell/bin/install_barclamp.rb cinder. For good measure delete the 
cinder.conf and restart chef-client. The DB and cinder.conf should be recreated 
with a new password at this time.

If the above method doesn't result in a success, please send us the logfile 
contents (including +-100 lines) before and after the relevant section. We'll 
be happy to take a closer look at things.

Hope this helps,
Simon


From: crowbar-bounces On Behalf Of Jacob, Jacob
Sent: Monday, September 30, 2013 4:36 PM
To: dsanpe...@mcna.net
Cc: crowbar
Subject: Re: [Crowbar] mesa-1.6 - cinder barclamp fails when applying proposal


Dell - Internal Use - Confidential
Hi Daniel,
   Looks like after you changed cinder.conf , the changes get reverted back to 
the wrong one when you re-applied the proposal.
 Let me try to reproduce this here.  Will keep you posted.
Thanks

Jacob M. Jacob
Software Dev Principal Engineer
Dell | Enterprise Cloud Solutions

From: crowbar-bounces On Behalf Of Daniel San Pedro
Sent: Monday, September 30, 2013 3:17 PM
To: crowbar
Subject: [Crowbar] mesa-1.6 - cinder barclamp fails when applying proposal

Hello,

I am running mesa-1.6_openstack-os-build.3459.dev. I am currently testing 
crowbar to use on our production environment. I am able to successfully apply 
the database, keystone, rabbitmq, and glance barclamps, but get hung up when 
applying cinder. I get the following error message in the logs and the proposal 
fails:

CRITICAL [cinder] (OperationalError) (1045, "Access denied for user 
'cinder'@'192.168.124.81' (using password: YES)")

Upon further research, I found that the MySQL password that the barclamp 
reports differs from what is cinder.conf
I have tried all of the below with no success:

 *   Synchronize passwords. I tried changing cinder.conf to the password found 
in the barclamp and reapplied, and vice versa
 *   I am able to login locally to MySQL using the cinder user and the password 
found in cinder.conf
 *   Edit 
/opt/dell/barclamps/cinder/chef/data_bags/crowbar/bc-template-cinder.json and 
manually add the password in the "db" section

Thanks!
--
Daniel San Pedro
Systems Administrator
MCNA Dental Plans
dsanpe...@mcna.net
Office: (800) 494-6262 Ext. 203

CONFIDENTIALITY NOTICE: This electronic mail may contain information that is 
privileged, confidential, and/or otherwise protected from disclosure to anyone 
other than its intended recipient(s). Any dissemination or use of this 
electronic mail or its contents by persons other than the intended recipient(s) 
is strictly prohibited. If you have received this communication in error, 
please notify the sender immediately by reply e-mail so that we may correct our 
internal records. Please then delete the original message. Thank you.
___
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/

Re: [Crowbar] Wrapping upstream stackforge cookbooks (proof of concept)

[Judd Maltin]

I think I'll be taking a good look at this in our coming sprints.

On Tue, Oct 1, 2013 at 1:35 PM,   wrote:
> Ionut,
>
> One of the major objectives for CB2 work has been to embrace the attribute
> injection style of cookbook so that we can align with Stackforge.
>
> Rob
>
> -Original Message-
> From: crowbar-bounces On Behalf Of Ionu? Ar?ari?i
> Sent: Tuesday, October 01, 2013 11:11 AM
> To: crowbar
> Subject: [Crowbar] Wrapping upstream stackforge cookbooks (proof of concept)
>
> Hello,
>
> I started working on a proof of concept to see if we could wrap the upstream
> stackforge cookbooks[1] in the existing barclamps.
>
> The stackforge cookbooks support the grizzly openstack branch. There are
> several advantages to using them: the style of the cookbooks is clearer and
> more orthogonal (e.g. platform-specific things are set in the attributes
> file), they have good chefspec test coverage and a growing community.
>
> I have a first working version up in a new branch in our SUSE-Cloud
> keystone-barclamp repository[2]. Some pieces aren't there yet, like password
> management and SSL support, but it works successfully with the other
> openstack barclamps in the release/pebbles/master branch.
>
> The code is pretty simple, it basically just maps some of the existing
> attributes from crowbar-names to stackforge-names. Basically all of it is in
> the default recipe[3]. I haven't changed any existing attribute names;
> changing those could reduce the size of the default recipe.
>
> So like I said, this is just a working proof of concept which we'd like to
> get some feedback on from the wider crowbar community to see if this would
> be a worthwhile path to follow.
>
> Thank you,
> Ionuț
>
> [1] https://launchpad.net/openstack-chef
> [2] https://github.com/SUSE-Cloud/barclamp-keystone/tree/stackforge-wrap
> [3]
> https://github.com/SUSE-Cloud/barclamp-keystone/blob/stackforge-wrap/chef/cookbooks/keystone/recipes/default.rb
>
> ___
> Crowbar mailing list
> Crowbar@dell.com
> https://lists.us.dell.com/mailman/listinfo/crowbar
> For more information: http://crowbar.github.com/
>
>
> ___
> Crowbar mailing list
> Crowbar@dell.com
> https://lists.us.dell.com/mailman/listinfo/crowbar
> For more information: http://crowbar.github.com/



-- 
Judd Maltin
T: 917-882-1270
F: 501-694-7809
what could possibly go wrong?

___
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/

Re: [Crowbar] mesa-1.6 - cinder barclamp fails when applying proposal

[Daniel San Pedro]

Thanks. I did not modify anything when deploying the cinder barclamp. It 
fails on the first try. Path:


Install crowbar OS.
Install Crowbar.
PXE boot two nodes: Controller and Compute
Rename and allocate nodes, wait for green light
Create proposals for each OpenStack barclamp except Swift and Tempest
Apply each proposal in order starting with the database barclamp to 
Controller node

Apply the cinder barclamp to controller node - failure

My test environment is as follows:
KVM Host
Crowbar admin node running as KVM guest
Two KVM guests PXE booting off the Crowbar admin node
One private virtual network that all guests can talk to each other on
One public network that the crowbar node has where I can access the GUI from

I received instructions from another Dell CloudEdge team member on 
making this work by editing the bc-template-network.json file before 
installing crowbar, and it works well.


I am currently running through the steps you outlined below and will 
report back my findings. Thanks once again.



   Daniel San Pedro
   Systems Administrator
   MCNA Dental Plans
   dsanpe...@mcna.net
   Office: (800) 494-6262 Ext. 203
   
   CONFIDENTIALITY NOTICE: This electronic mail may contain
   information that is privileged, confidential, and/or
   otherwise protected from disclosure to anyone other than its
   intended recipient(s). Any dissemination or use of this
   electronic mail or its contents by persons other than the
   intended recipient(s) is strictly prohibited. If you have
   received this communication in error, please notify the
   sender immediately by reply e-mail so that we may correct
   our internal records. Please then delete the original
   message. Thank you.

On 10/1/13 2:36 PM, simon_jake...@dell.com wrote:


Daniel,

we've taken a look at your issue, and we're having a hard time coming 
up with a path on how you got to where you are now. Specifically your 
second statement about being able to login with the cinder.conf 
password. None the less here are the things you can do to either fix 
this issues or provide more information to use:


We can try to recreate the cinder DB and reinitialize the password. In 
order to do so we recommend you stop chef-client from running on 
whichever node you have the DB located (which is typically the node 
that runs all the other MySQL DBs). Then you should drop the DB via 
the usual mysqladmin command. After we upload the whole Barclamp, this 
will reset all the associated Databags on the chef server, which is 
exactly what you want. You do this via: 
/opt/dell/bin/install_barclamp.rb cinder. For good measure delete the 
cinder.conf and restart chef-client. The DB and cinder.conf should be 
recreated with a new password at this time.


If the above method doesn't result in a success, please send us the 
logfile contents (including +-100 lines) before and after the relevant 
section. We'll be happy to take a closer look at things.


Hope this helps,

Simon

*From:*crowbar-bounces *On Behalf Of *Jacob, Jacob
*Sent:* Monday, September 30, 2013 4:36 PM
*To:* dsanpe...@mcna.net
*Cc:* crowbar
*Subject:* Re: [Crowbar] mesa-1.6 - cinder barclamp fails when 
applying proposal


*Dell - Internal Use - Confidential *

Hi Daniel,

 Looks like after you changed cinder.conf , the changes get reverted 
back to the wrong one when you re-applied the proposal.


 Let me try to reproduce this here.  Will keep you posted.

Thanks

Jacob M. Jacob

Software Dev Principal Engineer

*Dell*| Enterprise Cloud Solutions**

*From:*crowbar-bounces *On Behalf Of *Daniel San Pedro
*Sent:* Monday, September 30, 2013 3:17 PM
*To:* crowbar
*Subject:* [Crowbar] mesa-1.6 - cinder barclamp fails when applying 
proposal


Hello,

I am running mesa-1.6_openstack-os-build.3459.dev. I am currently 
testing crowbar to use on our production environment. I am able to 
successfully apply the database, keystone, rabbitmq, and glance 
barclamps, but get hung up when applying cinder. I get the following 
error message in the logs and the proposal fails:


/CRITICAL [cinder] (OperationalError) (1045, "Access denied for user 
'cinder'@'192.168.124.81' (using password: YES)")/


Upon further research, I found that the MySQL password that the 
barclamp reports differs from what is cinder.conf

I have tried all of the below with no success:

  * Synchronize passwords. I tried changing cinder.conf to the
password found in the barclamp and reapplied, and vice versa
  * I am able to login locally to MySQL using the cinder user and the
password found in cinder.conf
  * Edit
/opt/dell/barclamps/cinder/chef/data_bags/crowbar/bc-template-cinder.json
and manually add the password in the "db" section

Thanks!

--


Daniel San Pedro
Systems Administrator
MCNA Dental Plans
dsanpe...@mcna.net

Re: [Crowbar] mesa-1.6 - cinder barclamp fails when applying proposal

[Daniel San Pedro]

I can not locate /opt/dell/bin/install_barclamp.rb on the crowbar admin 
node nor on allocated node..



   Daniel San Pedro
   Systems Administrator
   MCNA Dental Plans
   dsanpe...@mcna.net
   Office: (800) 494-6262 Ext. 203
   
   CONFIDENTIALITY NOTICE: This electronic mail may contain
   information that is privileged, confidential, and/or
   otherwise protected from disclosure to anyone other than its
   intended recipient(s). Any dissemination or use of this
   electronic mail or its contents by persons other than the
   intended recipient(s) is strictly prohibited. If you have
   received this communication in error, please notify the
   sender immediately by reply e-mail so that we may correct
   our internal records. Please then delete the original
   message. Thank you.

On 10/1/13 4:37 PM, Daniel San Pedro wrote:
Thanks. I did not modify anything when deploying the cinder barclamp. 
It fails on the first try. Path:


Install crowbar OS.
Install Crowbar.
PXE boot two nodes: Controller and Compute
Rename and allocate nodes, wait for green light
Create proposals for each OpenStack barclamp except Swift and Tempest
Apply each proposal in order starting with the database barclamp to 
Controller node

Apply the cinder barclamp to controller node - failure

My test environment is as follows:
KVM Host
Crowbar admin node running as KVM guest
Two KVM guests PXE booting off the Crowbar admin node
One private virtual network that all guests can talk to each other on
One public network that the crowbar node has where I can access the 
GUI from


I received instructions from another Dell CloudEdge team member on 
making this work by editing the bc-template-network.json file before 
installing crowbar, and it works well.


I am currently running through the steps you outlined below and will 
report back my findings. Thanks once again.



Daniel San Pedro
Systems Administrator
MCNA Dental Plans
dsanpe...@mcna.net
Office: (800) 494-6262 Ext. 203

CONFIDENTIALITY NOTICE: This electronic mail may contain
information that is privileged, confidential, and/or
otherwise protected from disclosure to anyone other than
its intended recipient(s). Any dissemination or use of
this electronic mail or its contents by persons other than
the intended recipient(s) is strictly prohibited. If you
have received this communication in error, please notify
the sender immediately by reply e-mail so that we may
correct our internal records. Please then delete the
original message. Thank you.

On 10/1/13 2:36 PM, simon_jake...@dell.com wrote:


Daniel,

we've taken a look at your issue, and we're having a hard time coming 
up with a path on how you got to where you are now. Specifically your 
second statement about being able to login with the cinder.conf 
password. None the less here are the things you can do to either fix 
this issues or provide more information to use:


We can try to recreate the cinder DB and reinitialize the password. 
In order to do so we recommend you stop chef-client from running on 
whichever node you have the DB located (which is typically the node 
that runs all the other MySQL DBs). Then you should drop the DB via 
the usual mysqladmin command. After we upload the whole Barclamp, 
this will reset all the associated Databags on the chef server, which 
is exactly what you want. You do this via: 
/opt/dell/bin/install_barclamp.rb cinder. For good measure delete the 
cinder.conf and restart chef-client. The DB and cinder.conf should be 
recreated with a new password at this time.


If the above method doesn't result in a success, please send us the 
logfile contents (including +-100 lines) before and after the 
relevant section. We'll be happy to take a closer look at things.


Hope this helps,

Simon

*From:*crowbar-bounces *On Behalf Of *Jacob, Jacob
*Sent:* Monday, September 30, 2013 4:36 PM
*To:* dsanpe...@mcna.net
*Cc:* crowbar
*Subject:* Re: [Crowbar] mesa-1.6 - cinder barclamp fails when 
applying proposal


*Dell - Internal Use - Confidential *

Hi Daniel,

 Looks like after you changed cinder.conf , the changes get reverted 
back to the wrong one when you re-applied the proposal.


 Let me try to reproduce this here.  Will keep you posted.

Thanks

Jacob M. Jacob

Software Dev Principal Engineer

*Dell*| Enterprise Cloud Solutions**

*From:*crowbar-bounces *On Behalf Of *Daniel San Pedro
*Sent:* Monday, September 30, 2013 3:17 PM
*To:* crowbar
*Subject:* [Crowbar] mesa-1.6 - cinder barclamp fails when applying 
proposal


Hello,

I am running mesa-1.6_openstack-os-build.3459.dev. I am currently 
testing crowbar to use on our production envi

Re: [Crowbar] mesa-1.6 - cinder barclamp fails when applying proposal

[Simon_Jakesch]

My mistake it's actually barclamp_install.rb.


From: Daniel San Pedro [mailto:dsanpe...@mcna.net]
Sent: Tuesday, October 01, 2013 3:40 PM
To: Jakesch, Simon
Cc: Jacob, Jacob; crowbar
Subject: Re: [Crowbar] mesa-1.6 - cinder barclamp fails when applying proposal

I can not locate /opt/dell/bin/install_barclamp.rb on the crowbar admin node 
nor on allocated node..
Daniel San Pedro
Systems Administrator
MCNA Dental Plans
dsanpe...@mcna.net
Office: (800) 494-6262 Ext. 203

CONFIDENTIALITY NOTICE: This electronic mail may contain information that is 
privileged, confidential, and/or otherwise protected from disclosure to anyone 
other than its intended recipient(s). Any dissemination or use of this 
electronic mail or its contents by persons other than the intended recipient(s) 
is strictly prohibited. If you have received this communication in error, 
please notify the sender immediately by reply e-mail so that we may correct our 
internal records. Please then delete the original message. Thank you.
On 10/1/13 4:37 PM, Daniel San Pedro wrote:
Thanks. I did not modify anything when deploying the cinder barclamp. It fails 
on the first try. Path:

Install crowbar OS.
Install Crowbar.
PXE boot two nodes: Controller and Compute
Rename and allocate nodes, wait for green light
Create proposals for each OpenStack barclamp except Swift and Tempest
Apply each proposal in order starting with the database barclamp to Controller 
node
Apply the cinder barclamp to controller node - failure

My test environment is as follows:
KVM Host
Crowbar admin node running as KVM guest
Two KVM guests PXE booting off the Crowbar admin node
One private virtual network that all guests can talk to each other on
One public network that the crowbar node has where I can access the GUI from

I received instructions from another Dell CloudEdge team member on making this 
work by editing the bc-template-network.json file before installing crowbar, 
and it works well.

I am currently running through the steps you outlined below and will report 
back my findings. Thanks once again.
Daniel San Pedro
Systems Administrator
MCNA Dental Plans
dsanpe...@mcna.net
Office: (800) 494-6262 Ext. 203

CONFIDENTIALITY NOTICE: This electronic mail may contain information that is 
privileged, confidential, and/or otherwise protected from disclosure to anyone 
other than its intended recipient(s). Any dissemination or use of this 
electronic mail or its contents by persons other than the intended recipient(s) 
is strictly prohibited. If you have received this communication in error, 
please notify the sender immediately by reply e-mail so that we may correct our 
internal records. Please then delete the original message. Thank you.
On 10/1/13 2:36 PM, simon_jake...@dell.com wrote:
Daniel,

we've taken a look at your issue, and we're having a hard time coming up with a 
path on how you got to where you are now. Specifically your second statement 
about being able to login with the cinder.conf password. None the less here are 
the things you can do to either fix this issues or provide more information to 
use:

We can try to recreate the cinder DB and reinitialize the password. In order to 
do so we recommend you stop chef-client from running on whichever node you have 
the DB located (which is typically the node that runs all the other MySQL DBs). 
Then you should drop the DB via the usual mysqladmin command. After we upload 
the whole Barclamp, this will reset all the associated Databags on the chef 
server, which is exactly what you want. You do this via: 
/opt/dell/bin/install_barclamp.rb cinder. For good measure delete the 
cinder.conf and restart chef-client. The DB and cinder.conf should be recreated 
with a new password at this time.

If the above method doesn't result in a success, please send us the logfile 
contents (including +-100 lines) before and after the relevant section. We'll 
be happy to take a closer look at things.

Hope this helps,
Simon


From: crowbar-bounces On Behalf Of Jacob, Jacob
Sent: Monday, September 30, 2013 4:36 PM
To: dsanpe...@mcna.net
Cc: crowbar
Subject: Re: [Crowbar] mesa-1.6 - cinder barclamp fails when applying proposal


Dell - Internal Use - Confidential
Hi Daniel,
   Looks like after you changed cinder.conf , the changes get reverted back to 
the wrong one when you re-applied the proposal.
 Let me try to reproduce this here.  Will keep you posted.
Thanks

Jacob M. Jacob
Software Dev Principal Engineer
Dell | Enterprise Cloud Solutions

From: crowbar-bounces On Behalf Of Daniel San Pedro
Sent: Monday, September 30, 2013 3:17 PM
To: crowbar
Subject: [Crowbar] mesa-1.6 - cinder barclamp fails when applying proposal

Hello,

I am running mesa-1.6_openstack-os-build.3459.dev. I am currently testing 
crowbar to use on our production environment. I am able to successfull

Re: [Crowbar] Wrapping upstream stackforge cookbooks (proof of concept)

[Vincent Untz]

Le mardi 01 octobre 2013, à 12:35 -0500, rob_hirschf...@dell.com a écrit :
> Ionut,
> One of the major objectives for CB2 work has been to embrace the attribute 
> injection style of cookbook so that we can align with Stackforge.

I remember that we mentioned we'd do that post-Grizzly, even in Crowbar
1.x, when this was discussed in Portland. So I'd be in favor of doing
such a switch in Roxy (assuming it leads to no regression, obviously).

Cheers,

Vincent

> Rob
> 
> -Original Message-
> From: crowbar-bounces On Behalf Of Ionu? Ar?ari?i
> Sent: Tuesday, October 01, 2013 11:11 AM
> To: crowbar
> Subject: [Crowbar] Wrapping upstream stackforge cookbooks (proof of concept)
> 
> Hello,
> 
> I started working on a proof of concept to see if we could wrap the upstream 
> stackforge cookbooks[1] in the existing barclamps.
> 
> The stackforge cookbooks support the grizzly openstack branch. There are 
> several advantages to using them: the style of the cookbooks is clearer and 
> more orthogonal (e.g. platform-specific things are set in the attributes 
> file), they have good chefspec test coverage and a growing community.
> 
> I have a first working version up in a new branch in our SUSE-Cloud 
> keystone-barclamp repository[2]. Some pieces aren't there yet, like password 
> management and SSL support, but it works successfully with the other 
> openstack barclamps in the release/pebbles/master branch.
> 
> The code is pretty simple, it basically just maps some of the existing 
> attributes from crowbar-names to stackforge-names. Basically all of it is in 
> the default recipe[3]. I haven't changed any existing attribute names; 
> changing those could reduce the size of the default recipe.
> 
> So like I said, this is just a working proof of concept which we'd like to 
> get some feedback on from the wider crowbar community to see if this would be 
> a worthwhile path to follow.
> 
> Thank you,
> Ionuț
> 
> [1] https://launchpad.net/openstack-chef
> [2] https://github.com/SUSE-Cloud/barclamp-keystone/tree/stackforge-wrap
> [3]
> https://github.com/SUSE-Cloud/barclamp-keystone/blob/stackforge-wrap/chef/cookbooks/keystone/recipes/default.rb
> 
> ___
> Crowbar mailing list
> Crowbar@dell.com
> https://lists.us.dell.com/mailman/listinfo/crowbar
> For more information: http://crowbar.github.com/

> ___
> Crowbar mailing list
> Crowbar@dell.com
> https://lists.us.dell.com/mailman/listinfo/crowbar
> For more information: http://crowbar.github.com/


-- 
Les gens heureux ne sont pas pressés.

___
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/

Re: [Crowbar] Roles, nodes, noderoles, lifeycles, and events, oh my!

[Victor Lowther]

On Fri, Sep 27, 2013 at 1:32 PM, Shane Gibson wrote:

> Victor,
>
> ** **
>
> Thanks for the great write up.  One question … there is a brief mention of
> “an API request” – Are any of the APIs for the entire process exposed?  For
> example, would someone operating CB2 be able to manage it via API calls
> externally?  Our teams are very interested in the prospect of being able to
> do that.
>

All the API's that I am using are exposed, at least -- I am driving the
network and node APIs to create the initial admin node and to handle the
first part of the node discovery process in Sledgehammer.


> **
>
> Thanks,
>
> ~~shane 
>
> ** **
>
> ** **
>
> *From:* crowbar-boun...@dell.com [mailto:crowbar-boun...@dell.com] *On
> Behalf Of *victor_lowt...@dell.com
> *Sent:* Thursday, September 26, 2013 2:01 PM
> *To:* crow...@lists.us.dell.com
> *Subject:* [Crowbar] Roles, nodes, noderoles, lifeycles, and events, oh
> my!
>
> ** **
>
> ** **
>
> All nodes have roughly the same creation process:
>
> 1: an API request come in with the requested name of the new node, and
>
> ** **
>
> ___
> Crowbar mailing list
> Crowbar@dell.com
> https://lists.us.dell.com/mailman/listinfo/crowbar
> For more information: http://crowbar.github.com/
>
___
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/

Re: [Crowbar] few more merges into pebbles

[Arkady_Kanevsky]

Dell - Internal Use - Confidential
Sorry for wrong info.
The second pull is https://github.com/crowbar/barclamp-deployer/pull/157/

From: crowbar-bounces On Behalf Of Kanevsky, Arkady
Sent: Tuesday, October 01, 2013 10:34 AM
To: crowbar
Subject: [Crowbar] few more merges into pebbles

The following PRs have been merged into pebbles:
https://github.com/crowbar/barclamp-tempest/pull/47
https://github.com/crowbar/barclamp-tempest/pull/47

Will generate cherry picked PRs against Roxy today.
Thanks,
Arkady

[cid:image001.jpg@01CEBEC2.DA41EED0]


Arkady Kanevsky, Ph.D.

Director of SW Development

Enterprise Solution Group

+1 512 723 5264 | arkady_kanev...@dell.com



<>___
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/