Are people still using Opscode’s AWS cookbook, or is there a better one to
use?
I’m looking to automate the creation of provisioned IOPS volumes and that
cookbook doesn’t seem to do that. Additionally it seems to use an old
version of the right_aws Gem (and I’m not even sure if Rightscale is still
officially maintaining that). [1]
We use the opscode AWS cookbook and added some piops stuff, but haven't
upstreamed the changes. (bad devops, bad!) We're also using an older
version of the aws cookbook, so our changes can't even apply to the current
version, making it harder to upstream. I'm sorry I can't give you a better
answer, but yes, at least, we are using the opscode cookbook (and wish it
would handle piops on its own).
Maybe this is another candidate for the orphaned cookbooks list? It's got
three outstandand pull requests, the oldest being 8 months old.
-ben
On Wed, Jan 9, 2013 at 12:19 PM, Julian C. Dunn jdunn@aquezada.com wrote:
Are people still using Opscode's AWS cookbook, or is there a better one to
use?I'm looking to automate the creation of provisioned IOPS volumes and that
cookbook doesn't seem to do that. Additionally it seems to use an old
version of the right_aws Gem (and I'm not even sure if Rightscale is still
officially maintaining that). [1]
- Julian
I have a fork of the AWS cookbook with PIOPS support – unfortunately, it
contains a .gem snapshot of right_aws version 4.5 (built from a branch in
GitHub repository):
https://github.com/hectcastro/aws/tree/provisioned-iops
The corresponding open ticket in Jira:
http://tickets.opscode.com/browse/COOK-1595
At this point, the real solution may be to update the AWS cookbook so that
it uses the aws-sdk gem.
--
Hector
On Wed, Jan 9, 2013 at 3:40 PM, Ben Hartshorne ben@parse.com wrote:
We use the opscode AWS cookbook and added some piops stuff, but haven't
upstreamed the changes. (bad devops, bad!) We're also using an older
version of the aws cookbook, so our changes can't even apply to the current
version, making it harder to upstream. I'm sorry I can't give you a better
answer, but yes, at least, we are using the opscode cookbook (and wish it
would handle piops on its own).Maybe this is another candidate for the orphaned cookbooks list? It's got
three outstandand pull requests, the oldest being 8 months old.-ben
On Wed, Jan 9, 2013 at 12:19 PM, Julian C. Dunn jdunn@aquezada.comwrote:
Are people still using Opscode's AWS cookbook, or is there a better one
to use?I'm looking to automate the creation of provisioned IOPS volumes and that
cookbook doesn't seem to do that. Additionally it seems to use an old
version of the right_aws Gem (and I'm not even sure if Rightscale is still
officially maintaining that). [1]
- Julian
What cookbook are you referring to? Our Aws cookbook has three open pull requests. One was reviewed to be merged, one is a dupe that didn't have a CLA so a different one was merged and the third is a whitespace change but no ticket so we hadn't reviewed it yet.
If there are additional features that would benefit the community we'd love to have them. Please open a ticket if one isn't already opened for piops.
On Wednesday, January 9, 2013 at 13:40, Ben Hartshorne wrote:
We use the opscode AWS cookbook and added some piops stuff, but haven't upstreamed the changes. (bad devops, bad!) We're also using an older version of the aws cookbook, so our changes can't even apply to the current version, making it harder to upstream. I'm sorry I can't give you a better answer, but yes, at least, we are using the opscode cookbook (and wish it would handle piops on its own).
Maybe this is another candidate for the orphaned cookbooks list? It's got three outstandand pull requests, the oldest being 8 months old.
-ben
On Wed, Jan 9, 2013 at 12:19 PM, Julian C. Dunn <jdunn@aquezada.com (mailto:jdunn@aquezada.com)> wrote:
Are people still using Opscode's AWS cookbook, or is there a better one to use?
I'm looking to automate the creation of provisioned IOPS volumes and that cookbook doesn't seem to do that. Additionally it seems to use an old version of the right_aws Gem (and I'm not even sure if Rightscale is still officially maintaining that). [1]
- Julian
yup, that's the one. I didn't look in detail at the three open requests,
so I'm glad to hear that they're being watched.
As requested:
http://tickets.opscode.com/browse/COOK-2193 - Support for PIOPS
http://tickets.opscode.com/browse/COOK-2194 - Support for EBS Optimized
instances
-ben
On Wed, Jan 9, 2013 at 3:19 PM, Joshua Timberman joshua@opscode.com wrote:
What cookbook are you referring to? Our Aws cookbook has three open pull
requests. One was reviewed to be merged, one is a dupe that didn't have a
CLA so a different one was merged and the third is a whitespace change but
no ticket so we hadn't reviewed it yet.If there are additional features that would benefit the community we'd
love to have them. Please open a ticket if one isn't already opened for
piops.On Wednesday, January 9, 2013 at 13:40, Ben Hartshorne wrote:
We use the opscode AWS cookbook and added some piops stuff, but haven't
upstreamed the changes. (bad devops, bad!) We're also using an older
version of the aws cookbook, so our changes can't even apply to the current
version, making it harder to upstream. I'm sorry I can't give you a better
answer, but yes, at least, we are using the opscode cookbook (and wish it
would handle piops on its own).Maybe this is another candidate for the orphaned cookbooks list? It's got
three outstandand pull requests, the oldest being 8 months old.-ben
On Wed, Jan 9, 2013 at 12:19 PM, Julian C. Dunn jdunn@aquezada.comwrote:
Are people still using Opscode's AWS cookbook, or is there a better one to
use?I'm looking to automate the creation of provisioned IOPS volumes and that
cookbook doesn't seem to do that. Additionally it seems to use an old
version of the right_aws Gem (and I'm not even sure if Rightscale is still
officially maintaining that). [1]
- Julian
Thanks Ben. Do you have any code for those? Or if anyone else does, a pull request would be great :).
On Wednesday, January 9, 2013 at 16:42, Ben Hartshorne wrote:
yup, that's the one. I didn't look in detail at the three open requests, so I'm glad to hear that they're being watched.
As requested:
http://tickets.opscode.com/browse/COOK-2193 - Support for PIOPS
http://tickets.opscode.com/browse/COOK-2194 - Support for EBS Optimized instances
-ben
On Wed, Jan 9, 2013 at 3:19 PM, Joshua Timberman <joshua@opscode.com (mailto:joshua@opscode.com)> wrote:
What cookbook are you referring to? Our Aws cookbook has three open pull requests. One was reviewed to be merged, one is a dupe that didn't have a CLA so a different one was merged and the third is a whitespace change but no ticket so we hadn't reviewed it yet.
If there are additional features that would benefit the community we'd love to have them. Please open a ticket if one isn't already opened for piops.
On Wednesday, January 9, 2013 at 13:40, Ben Hartshorne wrote:
We use the opscode AWS cookbook and added some piops stuff, but haven't upstreamed the changes. (bad devops, bad!) We're also using an older version of the aws cookbook, so our changes can't even apply to the current version, making it harder to upstream. I'm sorry I can't give you a better answer, but yes, at least, we are using the opscode cookbook (and wish it would handle piops on its own).
Maybe this is another candidate for the orphaned cookbooks list? It's got three outstandand pull requests, the oldest being 8 months old.
-ben
On Wed, Jan 9, 2013 at 12:19 PM, Julian C. Dunn <jdunn@aquezada.com (mailto:jdunn@aquezada.com)> wrote:
Are people still using Opscode's AWS cookbook, or is there a better one to use?
I'm looking to automate the creation of provisioned IOPS volumes and that cookbook doesn't seem to do that. Additionally it seems to use an old version of the right_aws Gem (and I'm not even sure if Rightscale is still officially maintaining that). [1]
- Julian
It might be worth considering moving to the official AWS ruby gem
instead of right_aws and waiting for it to support features?
On Thu, Jan 10, 2013 at 11:12 AM, Joshua Timberman joshua@opscode.com wrote:
Thanks Ben. Do you have any code for those? Or if anyone else does, a pull
request would be great :).On Wednesday, January 9, 2013 at 16:42, Ben Hartshorne wrote:
yup, that's the one. I didn't look in detail at the three open requests, so
I'm glad to hear that they're being watched.As requested:
http://tickets.opscode.com/browse/COOK-2193 - Support for PIOPS
http://tickets.opscode.com/browse/COOK-2194 - Support for EBS Optimized
instances
-ben
On Wed, Jan 9, 2013 at 3:19 PM, Joshua Timberman joshua@opscode.com wrote:
What cookbook are you referring to? Our Aws cookbook has three open pull
requests. One was reviewed to be merged, one is a dupe that didn't have a
CLA so a different one was merged and the third is a whitespace change but
no ticket so we hadn't reviewed it yet.If there are additional features that would benefit the community we'd love
to have them. Please open a ticket if one isn't already opened for piops.On Wednesday, January 9, 2013 at 13:40, Ben Hartshorne wrote:
We use the opscode AWS cookbook and added some piops stuff, but haven't
upstreamed the changes. (bad devops, bad!) We're also using an older
version of the aws cookbook, so our changes can't even apply to the current
version, making it harder to upstream. I'm sorry I can't give you a better
answer, but yes, at least, we are using the opscode cookbook (and wish it
would handle piops on its own).Maybe this is another candidate for the orphaned cookbooks list? It's got
three outstandand pull requests, the oldest being 8 months old.-ben
On Wed, Jan 9, 2013 at 12:19 PM, Julian C. Dunn jdunn@aquezada.com wrote:
Are people still using Opscode's AWS cookbook, or is there a better one to
use?I'm looking to automate the creation of provisioned IOPS volumes and that
cookbook doesn't seem to do that. Additionally it seems to use an old
version of the right_aws Gem (and I'm not even sure if Rightscale is still
officially maintaining that). [1]
- Julian
"Official"? Which one is official?
On Thu, Jan 10, 2013 at 11:23 AM, John E. Vincent (lusis)
lusis.org+chef-list@gmail.com wrote:
It might be worth considering moving to the official AWS ruby gem
instead of right_aws and waiting for it to support features?On Thu, Jan 10, 2013 at 11:12 AM, Joshua Timberman joshua@opscode.com wrote:
Thanks Ben. Do you have any code for those? Or if anyone else does, a pull
request would be great :).On Wednesday, January 9, 2013 at 16:42, Ben Hartshorne wrote:
yup, that's the one. I didn't look in detail at the three open requests, so
I'm glad to hear that they're being watched.As requested:
http://tickets.opscode.com/browse/COOK-2193 - Support for PIOPS
http://tickets.opscode.com/browse/COOK-2194 - Support for EBS Optimized
instances
-ben
On Wed, Jan 9, 2013 at 3:19 PM, Joshua Timberman joshua@opscode.com wrote:
What cookbook are you referring to? Our Aws cookbook has three open pull
requests. One was reviewed to be merged, one is a dupe that didn't have a
CLA so a different one was merged and the third is a whitespace change but
no ticket so we hadn't reviewed it yet.If there are additional features that would benefit the community we'd love
to have them. Please open a ticket if one isn't already opened for piops.On Wednesday, January 9, 2013 at 13:40, Ben Hartshorne wrote:
We use the opscode AWS cookbook and added some piops stuff, but haven't
upstreamed the changes. (bad devops, bad!) We're also using an older
version of the aws cookbook, so our changes can't even apply to the current
version, making it harder to upstream. I'm sorry I can't give you a better
answer, but yes, at least, we are using the opscode cookbook (and wish it
would handle piops on its own).Maybe this is another candidate for the orphaned cookbooks list? It's got
three outstandand pull requests, the oldest being 8 months old.-ben
On Wed, Jan 9, 2013 at 12:19 PM, Julian C. Dunn jdunn@aquezada.com wrote:
Are people still using Opscode's AWS cookbook, or is there a better one to
use?I'm looking to automate the creation of provisioned IOPS volumes and that
cookbook doesn't seem to do that. Additionally it seems to use an old
version of the right_aws Gem (and I'm not even sure if Rightscale is still
officially maintaining that). [1]
- Julian
We're also using hectcastro's fork to get the piops. Seems to be working quite nicely 
@Mike I think the "official" gem they're referring to is: GitHub - aws/aws-sdk-ruby: The official AWS SDK for Ruby.
.m
On Jan 10, 2013, at 5:29 PM, Mike wrote:
"Official"? Which one is official?
On Thu, Jan 10, 2013 at 11:23 AM, John E. Vincent (lusis)
lusis.org+chef-list@gmail.com wrote:It might be worth considering moving to the official AWS ruby gem
instead of right_aws and waiting for it to support features?On Thu, Jan 10, 2013 at 11:12 AM, Joshua Timberman joshua@opscode.com wrote:
Thanks Ben. Do you have any code for those? Or if anyone else does, a pull
request would be great :).On Wednesday, January 9, 2013 at 16:42, Ben Hartshorne wrote:
yup, that's the one. I didn't look in detail at the three open requests, so
I'm glad to hear that they're being watched.As requested:
http://tickets.opscode.com/browse/COOK-2193 - Support for PIOPS
http://tickets.opscode.com/browse/COOK-2194 - Support for EBS Optimized
instances
-ben
On Wed, Jan 9, 2013 at 3:19 PM, Joshua Timberman joshua@opscode.com wrote:
What cookbook are you referring to? Our Aws cookbook has three open pull
requests. One was reviewed to be merged, one is a dupe that didn't have a
CLA so a different one was merged and the third is a whitespace change but
no ticket so we hadn't reviewed it yet.If there are additional features that would benefit the community we'd love
to have them. Please open a ticket if one isn't already opened for piops.On Wednesday, January 9, 2013 at 13:40, Ben Hartshorne wrote:
We use the opscode AWS cookbook and added some piops stuff, but haven't
upstreamed the changes. (bad devops, bad!) We're also using an older
version of the aws cookbook, so our changes can't even apply to the current
version, making it harder to upstream. I'm sorry I can't give you a better
answer, but yes, at least, we are using the opscode cookbook (and wish it
would handle piops on its own).Maybe this is another candidate for the orphaned cookbooks list? It's got
three outstandand pull requests, the oldest being 8 months old.-ben
On Wed, Jan 9, 2013 at 12:19 PM, Julian C. Dunn jdunn@aquezada.com wrote:
Are people still using Opscode's AWS cookbook, or is there a better one to
use?I'm looking to automate the creation of provisioned IOPS volumes and that
cookbook doesn't seem to do that. Additionally it seems to use an old
version of the right_aws Gem (and I'm not even sure if Rightscale is still
officially maintaining that). [1]
- Julian
Agreed. right_aws is also missing support for VPCs, so things like
autojoining load balancers won't work in a VPC.
Greg
On 01/10/2013 10:23 AM, John E. Vincent (lusis) wrote:
It might be worth considering moving to the official AWS ruby gem
instead of right_aws and waiting for it to support features?On Thu, Jan 10, 2013 at 11:12 AM, Joshua Timberman joshua@opscode.com wrote:
Thanks Ben. Do you have any code for those? Or if anyone else does, a pull
request would be great :).On Wednesday, January 9, 2013 at 16:42, Ben Hartshorne wrote:
yup, that's the one. I didn't look in detail at the three open requests, so
I'm glad to hear that they're being watched.As requested:
http://tickets.opscode.com/browse/COOK-2193 - Support for PIOPS
http://tickets.opscode.com/browse/COOK-2194 - Support for EBS Optimized
instances
-ben
On Wed, Jan 9, 2013 at 3:19 PM, Joshua Timberman joshua@opscode.com wrote:
What cookbook are you referring to? Our Aws cookbook has three open pull
requests. One was reviewed to be merged, one is a dupe that didn't have a
CLA so a different one was merged and the third is a whitespace change but
no ticket so we hadn't reviewed it yet.If there are additional features that would benefit the community we'd love
to have them. Please open a ticket if one isn't already opened for piops.On Wednesday, January 9, 2013 at 13:40, Ben Hartshorne wrote:
We use the opscode AWS cookbook and added some piops stuff, but haven't
upstreamed the changes. (bad devops, bad!) We're also using an older
version of the aws cookbook, so our changes can't even apply to the current
version, making it harder to upstream. I'm sorry I can't give you a better
answer, but yes, at least, we are using the opscode cookbook (and wish it
would handle piops on its own).Maybe this is another candidate for the orphaned cookbooks list? It's got
three outstandand pull requests, the oldest being 8 months old.-ben
On Wed, Jan 9, 2013 at 12:19 PM, Julian C. Dunn jdunn@aquezada.com wrote:
Are people still using Opscode's AWS cookbook, or is there a better one to
use?I'm looking to automate the creation of provisioned IOPS volumes and that
cookbook doesn't seem to do that. Additionally it seems to use an old
version of the right_aws Gem (and I'm not even sure if Rightscale is still
officially maintaining that). [1]
- Julian
What say you, Joshua/Opscode? Would taking a stab at replacing the
right_aws gem with the AWS-supported one be something you'd consider?
On Thu, Jan 10, 2013 at 11:54 AM, Greg Symons gsymons@drillinginfo.com wrote:
Agreed. right_aws is also missing support for VPCs, so things like
autojoining load balancers won't work in a VPC.Greg
On 01/10/2013 10:23 AM, John E. Vincent (lusis) wrote:
It might be worth considering moving to the official AWS ruby gem
instead of right_aws and waiting for it to support features?On Thu, Jan 10, 2013 at 11:12 AM, Joshua Timberman joshua@opscode.com
wrote:Thanks Ben. Do you have any code for those? Or if anyone else does, a
pull
request would be great :).On Wednesday, January 9, 2013 at 16:42, Ben Hartshorne wrote:
yup, that's the one. I didn't look in detail at the three open requests,
so
I'm glad to hear that they're being watched.As requested:
http://tickets.opscode.com/browse/COOK-2193 - Support for PIOPS
http://tickets.opscode.com/browse/COOK-2194 - Support for EBS Optimized
instances
-ben
On Wed, Jan 9, 2013 at 3:19 PM, Joshua Timberman joshua@opscode.com
wrote:What cookbook are you referring to? Our Aws cookbook has three open pull
requests. One was reviewed to be merged, one is a dupe that didn't have a
CLA so a different one was merged and the third is a whitespace change
but
no ticket so we hadn't reviewed it yet.If there are additional features that would benefit the community we'd
love
to have them. Please open a ticket if one isn't already opened for piops.On Wednesday, January 9, 2013 at 13:40, Ben Hartshorne wrote:
We use the opscode AWS cookbook and added some piops stuff, but haven't
upstreamed the changes. (bad devops, bad!) We're also using an older
version of the aws cookbook, so our changes can't even apply to the
current
version, making it harder to upstream. I'm sorry I can't give you a
better
answer, but yes, at least, we are using the opscode cookbook (and wish it
would handle piops on its own).Maybe this is another candidate for the orphaned cookbooks list? It's
got
three outstandand pull requests, the oldest being 8 months old.-ben
On Wed, Jan 9, 2013 at 12:19 PM, Julian C. Dunn jdunn@aquezada.com
wrote:Are people still using Opscode's AWS cookbook, or is there a better one
to
use?I'm looking to automate the creation of provisioned IOPS volumes and that
cookbook doesn't seem to do that. Additionally it seems to use an old
version of the right_aws Gem (and I'm not even sure if Rightscale is
still
officially maintaining that). [1]
- Julian
For the record, it appears that RightScale is actually keeping up with AWS
feature additions – they just aren't cutting new versions of the gem. This
is why I had to take a snapshot of their GitHub repository and create a
.gem from that.
All of that said, I agree that moving to the official AWS Ruby SDK is the
best long-term solution.
--
Hector
On Thu, Jan 10, 2013 at 1:54 PM, Mike miketheman@gmail.com wrote:
What say you, Joshua/Opscode? Would taking a stab at replacing the
right_aws gem with the AWS-supported one be something you'd consider?On Thu, Jan 10, 2013 at 11:54 AM, Greg Symons gsymons@drillinginfo.com
wrote:Agreed. right_aws is also missing support for VPCs, so things like
autojoining load balancers won't work in a VPC.Greg
On 01/10/2013 10:23 AM, John E. Vincent (lusis) wrote:
It might be worth considering moving to the official AWS ruby gem
instead of right_aws and waiting for it to support features?On Thu, Jan 10, 2013 at 11:12 AM, Joshua Timberman joshua@opscode.com
wrote:Thanks Ben. Do you have any code for those? Or if anyone else does, a
pull
request would be great :).On Wednesday, January 9, 2013 at 16:42, Ben Hartshorne wrote:
yup, that's the one. I didn't look in detail at the three open
requests,
so
I'm glad to hear that they're being watched.As requested:
http://tickets.opscode.com/browse/COOK-2193 - Support for PIOPS
http://tickets.opscode.com/browse/COOK-2194 - Support for EBS
Optimized
instances
-ben
On Wed, Jan 9, 2013 at 3:19 PM, Joshua Timberman joshua@opscode.com
wrote:What cookbook are you referring to? Our Aws cookbook has three open
pull
requests. One was reviewed to be merged, one is a dupe that didn't
have a
CLA so a different one was merged and the third is a whitespace change
but
no ticket so we hadn't reviewed it yet.If there are additional features that would benefit the community we'd
love
to have them. Please open a ticket if one isn't already opened for
piops.On Wednesday, January 9, 2013 at 13:40, Ben Hartshorne wrote:
We use the opscode AWS cookbook and added some piops stuff, but haven't
upstreamed the changes. (bad devops, bad!) We're also using an older
version of the aws cookbook, so our changes can't even apply to the
current
version, making it harder to upstream. I'm sorry I can't give you a
better
answer, but yes, at least, we are using the opscode cookbook (and wish
it
would handle piops on its own).Maybe this is another candidate for the orphaned cookbooks list? It's
got
three outstandand pull requests, the oldest being 8 months old.-ben
On Wed, Jan 9, 2013 at 12:19 PM, Julian C. Dunn jdunn@aquezada.com
wrote:Are people still using Opscode's AWS cookbook, or is there a better one
to
use?I'm looking to automate the creation of provisioned IOPS volumes and
that
cookbook doesn't seem to do that. Additionally it seems to use an old
version of the right_aws Gem (and I'm not even sure if Rightscale is
still
officially maintaining that). [1]
- Julian
I have one data point that may be of use. We use eucalyptus internally,
which is intended to be API compatible with AWS. It works exceedingly well.
The only thing we've had any trouble with is swapping these gems to point
to eucalyptus instead. The newest versions of the fog gem have made this
very simple, and it's what we've built our aws cookbook, tooling, etc
around.
I think it's likely best to keep in mind that these tools will be used with
Eucalyptus too. The more they interop, the better.
On Fri, Jan 11, 2013 at 4:10 PM, Hector Castro hectcastro@gmail.com wrote:
For the record, it appears that RightScale is actually keeping up with AWS
feature additions – they just aren't cutting new versions of the gem. This
is why I had to take a snapshot of their GitHub repository and create a
.gem from that.All of that said, I agree that moving to the official AWS Ruby SDK is the
best long-term solution.--
HectorOn Thu, Jan 10, 2013 at 1:54 PM, Mike miketheman@gmail.com wrote:
What say you, Joshua/Opscode? Would taking a stab at replacing the
right_aws gem with the AWS-supported one be something you'd consider?On Thu, Jan 10, 2013 at 11:54 AM, Greg Symons gsymons@drillinginfo.com
wrote:Agreed. right_aws is also missing support for VPCs, so things like
autojoining load balancers won't work in a VPC.Greg
On 01/10/2013 10:23 AM, John E. Vincent (lusis) wrote:
It might be worth considering moving to the official AWS ruby gem
instead of right_aws and waiting for it to support features?On Thu, Jan 10, 2013 at 11:12 AM, Joshua Timberman <joshua@opscode.com
wrote:
Thanks Ben. Do you have any code for those? Or if anyone else does, a
pull
request would be great :).On Wednesday, January 9, 2013 at 16:42, Ben Hartshorne wrote:
yup, that's the one. I didn't look in detail at the three open
requests,
so
I'm glad to hear that they're being watched.As requested:
http://tickets.opscode.com/browse/COOK-2193 - Support for PIOPS
http://tickets.opscode.com/browse/COOK-2194 - Support for EBS
Optimized
instances
-ben
On Wed, Jan 9, 2013 at 3:19 PM, Joshua Timberman joshua@opscode.com
wrote:What cookbook are you referring to? Our Aws cookbook has three open
pull
requests. One was reviewed to be merged, one is a dupe that didn't
have a
CLA so a different one was merged and the third is a whitespace change
but
no ticket so we hadn't reviewed it yet.If there are additional features that would benefit the community we'd
love
to have them. Please open a ticket if one isn't already opened for
piops.On Wednesday, January 9, 2013 at 13:40, Ben Hartshorne wrote:
We use the opscode AWS cookbook and added some piops stuff, but
haven't
upstreamed the changes. (bad devops, bad!) We're also using an older
version of the aws cookbook, so our changes can't even apply to the
current
version, making it harder to upstream. I'm sorry I can't give you a
better
answer, but yes, at least, we are using the opscode cookbook (and
wish it
would handle piops on its own).Maybe this is another candidate for the orphaned cookbooks list? It's
got
three outstandand pull requests, the oldest being 8 months old.-ben
On Wed, Jan 9, 2013 at 12:19 PM, Julian C. Dunn jdunn@aquezada.com
wrote:Are people still using Opscode's AWS cookbook, or is there a better
one
to
use?I'm looking to automate the creation of provisioned IOPS volumes and
that
cookbook doesn't seem to do that. Additionally it seems to use an old
version of the right_aws Gem (and I'm not even sure if Rightscale is
still
officially maintaining that). [1]
- Julian
@Kevin – I think the main opposition to using Fog for the AWS cookbook
is the number of gem dependencies it introduces. Your point about
Eucalyptus interoperability is certainly valid – not sure how well the
Ruby AWS SDK handles this.
--
Hector
On Sat, Jan 12, 2013 at 5:36 PM, Kevin Nuckolls
kevin.nuckolls@gmail.com wrote:
I have one data point that may be of use. We use eucalyptus internally,
which is intended to be API compatible with AWS. It works exceedingly well.
The only thing we've had any trouble with is swapping these gems to point to
eucalyptus instead. The newest versions of the fog gem have made this very
simple, and it's what we've built our aws cookbook, tooling, etc around.I think it's likely best to keep in mind that these tools will be used with
Eucalyptus too. The more they interop, the better.On Fri, Jan 11, 2013 at 4:10 PM, Hector Castro hectcastro@gmail.com wrote:
For the record, it appears that RightScale is actually keeping up with AWS
feature additions – they just aren't cutting new versions of the gem. This
is why I had to take a snapshot of their GitHub repository and create a .gem
from that.All of that said, I agree that moving to the official AWS Ruby SDK is the
best long-term solution.--
HectorOn Thu, Jan 10, 2013 at 1:54 PM, Mike miketheman@gmail.com wrote:
What say you, Joshua/Opscode? Would taking a stab at replacing the
right_aws gem with the AWS-supported one be something you'd consider?On Thu, Jan 10, 2013 at 11:54 AM, Greg Symons gsymons@drillinginfo.com
wrote:Agreed. right_aws is also missing support for VPCs, so things like
autojoining load balancers won't work in a VPC.Greg
On 01/10/2013 10:23 AM, John E. Vincent (lusis) wrote:
It might be worth considering moving to the official AWS ruby gem
instead of right_aws and waiting for it to support features?On Thu, Jan 10, 2013 at 11:12 AM, Joshua Timberman
joshua@opscode.com
wrote:Thanks Ben. Do you have any code for those? Or if anyone else does, a
pull
request would be great :).On Wednesday, January 9, 2013 at 16:42, Ben Hartshorne wrote:
yup, that's the one. I didn't look in detail at the three open
requests,
so
I'm glad to hear that they're being watched.As requested:
http://tickets.opscode.com/browse/COOK-2193 - Support for PIOPS
http://tickets.opscode.com/browse/COOK-2194 - Support for EBS
Optimized
instances
-ben
On Wed, Jan 9, 2013 at 3:19 PM, Joshua Timberman joshua@opscode.com
wrote:What cookbook are you referring to? Our Aws cookbook has three open
pull
requests. One was reviewed to be merged, one is a dupe that didn't
have a
CLA so a different one was merged and the third is a whitespace
change
but
no ticket so we hadn't reviewed it yet.If there are additional features that would benefit the community
we'd
love
to have them. Please open a ticket if one isn't already opened for
piops.On Wednesday, January 9, 2013 at 13:40, Ben Hartshorne wrote:
We use the opscode AWS cookbook and added some piops stuff, but
haven't
upstreamed the changes. (bad devops, bad!) We're also using an
older
version of the aws cookbook, so our changes can't even apply to the
current
version, making it harder to upstream. I'm sorry I can't give you a
better
answer, but yes, at least, we are using the opscode cookbook (and
wish it
would handle piops on its own).Maybe this is another candidate for the orphaned cookbooks list?
It's
got
three outstandand pull requests, the oldest being 8 months old.-ben
On Wed, Jan 9, 2013 at 12:19 PM, Julian C. Dunn jdunn@aquezada.com
wrote:Are people still using Opscode's AWS cookbook, or is there a better
one
to
use?I'm looking to automate the creation of provisioned IOPS volumes and
that
cookbook doesn't seem to do that. Additionally it seems to use an old
version of the right_aws Gem (and I'm not even sure if Rightscale is
still
officially maintaining that). [1]
- Julian
At one point I delved deep into the ruby aws gem code. The trick was to
find where it constructs the URL for API access and instead change that to
you internal eucalyptus API endpoint. One more interesting note that took
me awhile to discover was that eucalyptus matches an older aws API version.
That needed to be overridden as well.
I found the innards of the ruby aws code to be a bit over complicated as
far as fixing that bug was concerned, which makes sense as the original
author likely never meant for that part to be patched. Anyway I ended up
using fog for my purposes. It already exposed the API endpoint and API
version as parameters I could just pass in. Rather convenient.
I did the minimal amount of work to get this working. We had to patch the
knife-eucalyptus plugin. In retrospect I wish I had spent time making the
knife-ec2 plugin more general instead of continuing to perpetuate the
Balkanized tooling that knife-ec2 and knife-eucalyptus represent. One of my
co-workers is actively working on getting the aws cookbook working with
eucalyptus as well using the fog gem. The dependencies aren't that big of a
deal IMO.
That said, yeah I'd prefer that the library cookbooks for aws interop use
the official ruby aws gem. Someone just needs to roll up their sleeves and
get that gem patched so you can use it with eucalyptus. Maybe that'll be
me? Maybe some other brave soul?
Hope that's helpful context.
Kevin Nuckolls
@knuckolls
On Sunday, January 13, 2013, Hector Castro wrote:
@Kevin – I think the main opposition to using Fog for the AWS cookbook
is the number of gem dependencies it introduces. Your point about
Eucalyptus interoperability is certainly valid – not sure how well the
Ruby AWS SDK handles this.--
HectorOn Sat, Jan 12, 2013 at 5:36 PM, Kevin Nuckolls
kevin.nuckolls@gmail.com wrote:I have one data point that may be of use. We use eucalyptus internally,
which is intended to be API compatible with AWS. It works exceedingly
well.
The only thing we've had any trouble with is swapping these gems to
point to
eucalyptus instead. The newest versions of the fog gem have made this
very
simple, and it's what we've built our aws cookbook, tooling, etc around.I think it's likely best to keep in mind that these tools will be used
with
Eucalyptus too. The more they interop, the better.On Fri, Jan 11, 2013 at 4:10 PM, Hector Castro hectcastro@gmail.com
wrote:For the record, it appears that RightScale is actually keeping up with
AWS
feature additions – they just aren't cutting new versions of the gem.
This
is why I had to take a snapshot of their GitHub repository and create a
.gem
from that.All of that said, I agree that moving to the official AWS Ruby SDK is
the
best long-term solution.--
HectorOn Thu, Jan 10, 2013 at 1:54 PM, Mike miketheman@gmail.com wrote:
What say you, Joshua/Opscode? Would taking a stab at replacing the
right_aws gem with the AWS-supported one be something you'd consider?On Thu, Jan 10, 2013 at 11:54 AM, Greg Symons <
gsymons@drillinginfo.com>
wrote:Agreed. right_aws is also missing support for VPCs, so things like
autojoining load balancers won't work in a VPC.Greg
On 01/10/2013 10:23 AM, John E. Vincent (lusis) wrote:
It might be worth considering moving to the official AWS ruby gem
instead of right_aws and waiting for it to support features?On Thu, Jan 10, 2013 at 11:12 AM, Joshua Timberman
joshua@opscode.com
wrote:Thanks Ben. Do you have any code for those? Or if anyone else
does, a
pull
request would be great :).On Wednesday, January 9, 2013 at 16:42, Ben Hartshorne wrote:
yup, that's the one. I didn't look in detail at the three open
requests,
so
I'm glad to hear that they're being watched.As requested:
http://tickets.opscode.com/browse/COOK-2193 - Support for PIOPS
http://tickets.opscode.com/browse/COOK-2194 - Support for EBS
Optimized
instances
-ben
On Wed, Jan 9, 2013 at 3:19 PM, Joshua Timberman <
joshua@opscode.com>
wrote:What cookbook are you referring to? Our Aws cookbook has three open
pull
requests. One was reviewed to be merged, one is a dupe that didn't
have a
CLA so a different one was merged and the third is a whitespace
change
but
no ticket so we hadn't reviewed it yet.
--
Sent from my cellular telephone