I'm getting "One or more of the requested capabilities are not supported." error when trying to mount a volume from Amazon EFS on AWS FARGATE.
Edit your service and update "Platform version" to 1.4.0
You can do this in terraform by adding an optional variable platform_version to the aws_ecs_service resource
Here is the official AWS communication about the platform version 1.4.0
Here is an important quote:
The primer blog post goes into more detail about the philosophy behind why we introduced Fargate platform versions and, for example, the practical reasons why we are not tagging platform version 1.4.0 as LATEST just yet.
The primer blog post is here. Keep the focus on this "critical" point:
Starting with the introduction of this platform version (1.4.0), we will hold on moving the LATEST tag. We want to provide a runway for users that use LATEST as an additional precaution. This means that if you are deploying today using the tag LATEST to identify a Fargate platform version, the system will keep referencing platform version 1.3.0 for now (albeit, technically, the latest platform version available today is 1.4.0).
These users could either start experimenting with 1.4.0 by explicitly deploying to it or wait until we move the tag LATEST to point to platform version 1.4.0. [Updated on 6/17/2020] We plan to make this change in the May 2020 time frame We plan to make this change at some point in Q3/2020, thus giving customers [Updated on 6/17/2020] about a month a few months to test 1.4.0 before it gets tagged as LATEST. Expect a formal announcement for this change.
This is intended to give users a window of time to test 1.4.0 without being forced to use it if they use the tag LATEST. We do not anticipate disruption but we decided to be conservative.
That's why you should use, at the time of writing, version 1.4.0, instead of LATEST in order to use AWS EFS.
Related
I'm trying to update the version of Optaplanner Vehicle routing here at the company I work for and I'm having difficulties. I noticed that the latest version installed here is the:
Implementation-Version: 7.6.0.Final
And we used two important services that are no longer available:
RouteAPI ===> https://github.com/kiegroup/optaplanner/routeapi
menorkm ===> https://github.com/kiegroup/optaplanner/menorkm
Is it possible to find the .war of these services updated today? Where?
Finally, I want to use the system in the similar to what you see in this link:
http://xxx.xx.x.xxx/routeapi/vehiclerouting/leaflet.jsp
How do i proceed?
Take a look at optaweb-vehicle-routing and the upgrade recipe to upgrade to 8.
I used halyard version 0.42.0-20180302093153 and Spinnaker version 1.6.0.
Is there any way that makes me to use hal command: hal deploy apply offline ?
Although there was no ability to do this when you asked your question, there's been work on this since then, under https://github.com/spinnaker/spinnaker/issues/2640. Presumably at some point this will get officially released and the documentation will be updated accordingly, but as of today it appears to be in a "coming, but not here yet" state.
I want to know what is the difference between installing HortonWorks HDP vs installing the components directly from Apache projects? One thing I can think of is that Horton works probably has the packages aligned so that the version of each component is compatible with that of the others within the suite, while getting them directly from Apache projects, I may have to handle version compatibility myself. Is that correct? Is there any other difference involved ignoring the support subscription aspect of it.
Thanks.
There are a lot of differences between "roll your own" and using a distribution. Some of the most obvious include:
All of the various components and versions have been tested and built to work together - incompatibility between versions (e.g. Hive, Hadoop, Spark, etc.) can be a painful problem to sort through on your own
Most distribution providers, including Hortonworks, will bring patches in from unstable releases into stable releases, so even for the "same" version (e.g. Hive 1.2.1) you're getting a better release than vanilla - these can include both bug fixes and "safe" feature changes
Most distribution providers, including Hortonworks, provide some flavor of centralized platform management. I'm a big fan of Ambari (the one that comes with HDP), for example - it makes configuration and monitoring significantly easier than coordinating a vanilla install
I would strongly recommend against trying to deploy vanilla, unless it's just for learning and playing. HDP community edition is free (both definitions) and a major improvement over doing it yourself. My last deployment of HDP was entirely based on the community edition.
My standard route has been to go to confluence, find the docs sections, then navigate through to the install docs for the version, e.g. sakai 10:
https://confluence.sakaiproject.org/x/iYGLBQ
Through one means or another I happened across the source route to this too, so starting here....
http://source.sakaiproject.org/release/
You get redirected to the latest stuff, and appended version numbers to that url gives you other docs, e.g. adding 2.8.2 or 10 to the end of the url
But the links to what I should download are quite often not there, at the time of writing the 10 tar ball and zip in the confluence links are dead and the source.sakaiproject links doesn't have the 10 docs yet (redirects to 2.9.3) presumably this is because v10 is not released yet....
So, I'd like to evaluate a new version of a sakai source install, what's the best way to do this? (considering the official documentation for install is still being formed)
Do I download the latest SVN, or the latest RC or the latest beta or??? How do I know what's best to test against without being "too" bleeding edge? Is there a recommended tar ball/zip link to test against? Is there a "latest good" SVN branch?
The latest code is always in the Sakai trunk (currently svn):
https://source.sakaiproject.org/svn/sakai/trunk/
That code may very well not be stable though as it is where things are being actively developed. If you are not actively developing then you should stick to the releases as indicated on the project website here:
http://sakaiproject.org/current-release
If you want to use something in between (say an upcoming release) then you can grab the most recent tag or maybe use a recent branch (both currently in svn, latest shown below at the time I write this):
https://source.sakaiproject.org/svn/sakai/branches/sakai-10.x/
https://source.sakaiproject.org/svn/sakai/tags/sakai-10-rc02/
The reality of the situation is that if you want to use something other than the release then you should really participate in the dev community for Sakai. Joining the mailing lists and the weekly calls will provide the information you are asking about and much more.
When i try to use the statement google.load("dojo", "1.6.1") in a web app I am developing, I receive the error:
Module: 'dojo' with version '1.6.1' not found!
This latest version of dojo, enables a certain amount of support for IE 9.0, and that is why I need to reference it. Is this supported by Google as a library? Either way, if anyone has suggestions as to how I can work around this?
1.6.1 is not yet in the Google ajax library repositories. See the latest version note here. I'm sure it will be within a day or two. There is a note on the dojo download page in big red letters saying that the CDN's are still behind on 1.6.0 and saying where to get notified when they are updated.
You can always use the "1.6" nomenclature to always have the latest version and your app will move up to 1.6.1 as soon as it hits the Google CDN. If a couple days is really going to make or break you you should consider compiling and using your own local version. Dojo makes this really easy.