-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ruby 2.3.0 #358
Comments
+1 on this |
Also +1 |
yes please, +1 |
@spickermann Thanks for asking, but there's nothing you could do to support us. Adding support for another Ruby version comprises more than just changing these cookbooks, and all the other repositories that corresponding changes aren't open to the public. Bear with us, it's on our radar. |
+1 Would really like to deploy 2.3. Thanks. |
+1 on this |
👍 |
Please 2.3 thanks |
Ruby 2.4 please. (Asking in advance because it might take ages too) |
Seeing that it's been 4 weeks since anyone at Amazon has responded to this thread should I forward this thread to AWS Business Support? Should I just override the default rails recipes and deploy rbenv? Because this is getting a bit ridiculous. Happy to help if you need engineering support. |
+1 |
1 similar comment
+1 |
crickets On Tue, Mar 22, 2016 at 8:57 PM, Sim Kern Cheh [email protected]
|
Ruby 2.3 is available for three months now, but still not available on OpsWorks. The HAProxy version installed by the cookbooks is several versions behind and soon out of maintenance. Just to mention two cookbooks which the community waits to be updated for a longer period of time and that are important parts of almost every Rails stack. There were no significant updates to the built-in Chef 11.4 cookbooks since Amazon announced that OpsWorks will support Chef 12, but without built-in cookbooks. I wonder if there are any plans to continue maintenance of the build-in cookbooks at all? It is okay if there won't be any updates in the future. But it would be great when there was some communication about the roadmap of OpsWorks: Does it makes sense to wait for a major update or should the community switch to Chef 12 or any other option... |
We definitely recommend to upgrade to Chef 12. Even though you might need to spend a little bit more effort initially as there are no built-in cookbooks, we believe that Chef 12 offers a lot more benefits. For example, it is much more compatible with the Chef community cookbooks, the OpsWorks and customer Chef run are separate and the agent & Chef integration is much improved. In Chef you can use the latest version of HAProxy or Ruby without being dependent on us updating or supporting exactly the version you need. You have a lot more freedom and can leverage the large number of community cookbooks, e.g. https://supermarket.chef.io/cookbooks/haproxy or https://supermarket.chef.io/cookbooks/br-ruby Chef 11.10 is still supported and we are slowly phasing out Chef 11.4. But you will not see big updates for Chef 11.10, mostly bug fixes and security updates. That said, we are evaluating to add support for Ruby 2.3 and Nodejs 4/5 for Chef 11.10. |
"A little bit more effort". "Use community cookbooks". Perhaps the product manager doesn't realise this adds up to "go evaluate the alternatives" to real customers with limited time and real security concerns. We chose OpsWorks to have professionally maintained Rails stack deploy cookbooks that were for AWS, by AWS. The supervisor layer above that is just a "nice to have". If I have to curate my own primary stack cookbooks now, I don't even know what OpsWorks is for. |
Yeah. This is really frustrating. You had one job. 😢 👎 |
Ruby 2.3.1 was released on 2016-04-26. |
+1 on this. |
+1 |
Has anybody found/created a cookbook for working around this on Chef 11.10? |
Hey, I created a cookbook for Opsworks Chef 12 to address this particular issue. It supports most common cases, and multiple rubies (including 2.3). I tried to make them as modular as possible, so if something is missing, you are very welcome to add your own plugins to them. I tested them against some of my projects (both commercial and private ones) and they seem pretty stable. The project is available as opsworks_ruby@github and as opsworks_ruby@supermarket. |
@ajgon thanks for doing this. I read the code and noticed that your opsworks_ruby package includes a lightweight framework for recipes that specifically target the OpsWorks platform and lifecycle. Have you considered extracting that and making it available separately? It's the missing piece that the AWS OpsWorks team should have delivered to help customers manage the transition. |
@ajgon great job. Amazon AWS/OpsWorks: Shame on you. You had one job! Sent from my iPhone
|
Is it happening? 9c916fa 🎉 |
@kitop Now you ruined the surprise. But yes, it's happening. |
Sorry, and thank you @githuesch! |
@kitop I was kidding. One thing to keep in mind, however, is that this change to the cookbooks isn't all it takes to get support for Ruby 2.3 out. We're in fact rolling out an agent with this change right now, but there will be a few more changes before Ruby 2.3 is an option you can select on your Rails layer. I'll update this issue once all of that is released. |
+1 |
Thanks, how do you feel about adding Ruby 2.4.0.pre too, when you are already working on Ruby version? |
^ indeed. If they work on supporting 2.4 now we won't have to wait 6 more months when 2.4 is released. |
Ruby 2.3 is now an option in the Rails layer. |
Heads up that I had OpsWorks failures (both deploys and Update Dependencies) until I upgraded my OpsWorks agent to 3438 (which in retrospect is obvious, since it included whatever changes were necessary for running Ruby 2.3, per the CHANGELOG). So if you see errors like this (note lack of version numbers in the .deb URL) and you're pinned to a particular OpsWorks agent version, upgrade to at least 3438:
|
When I see the contents of |
here is the log
|
Also worth noting, the 2015.09 Amazon AMI's dont have Ruby 2.3.1 listed in any of its packages. So far working with the 2016.09 AMI's |
@Janther how do you set the Ruby version? The missing version numbers in the URL you are trying to access are suspicious: https://opsworks-instance-assets-ap-southeast-2.s3.amazonaws.com/packages/ubuntu/14.04/opsworks-ruby._-_amd64.deb It should be 2.3.1 |
@jweiss did you ever get an answer for this? running into same issue. tried creating a new instance which also did not work |
do you have the OpsWorks instance and stack IDs for me please |
@jweiss My symptom is i am getting the same above error with the URL and no version number. i updated to 2.2 successfully today instead. I have the opsworks agent version set to "Latest Version" |
you're overwriting the default cookbooks with a version that was forked before ruby 2.3 support was introduced. Please check the file "ruby/attributes/ruby.rb" on both your cookbooks and the current opsworks repository |
which list of packages do you have in mind? Btw. ruby packages installed by OpsWorks are managed via chef cookbooks and not managed via package manager repos, so you'll probably not find them there. |
This thread was originally opened for Ruby 2.3. Can the people interested in Ruby 2.4 please +1 #403? That allows us to accurately determine the demand. Thanks! |
Yes to 2.4. Yes to 2.5. Yes to 2.6. Just keep going.
…On Thu, Jan 5, 2017 at 8:23 AM, githuesch ***@***.***> wrote:
This thread was originally opened for Ruby 2.3. Can the people interested
in Ruby 2.4 please +1 #403
<#403>? That allows us to
accurately determine the demand. Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#358 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AANxPGYPfCcS5dZ6dN3uiSJvu3vxMN-fks5rPRkKgaJpZM4G-K-6>
.
|
According to documentation Ruby 2.3 is already supported via chef 11.10: http://docs.aws.amazon.com/opsworks/latest/userguide/workingcookbook-ruby.html |
@interpegasus Right. I also announced it in this thread, right here. |
how does one fix ? /usr/lib/ruby/2.3.0/psych.rb:474:in |
Closing as we are tracking Ruby 2.5.0 here #421 |
How is work progressing for supporting Ruby 2.3.0 in Ruby and Ruby On Rails apps? Is there something we could do to support you?
Update: Ruby 2.3.1 was released on 2016-04-26.
The text was updated successfully, but these errors were encountered: