I am trying to use ECS optimized image (Amazon linux) and trying to install Glusterfs client on it.
Followed few documents like this internet but all are giving issue with repository. Unable to find the correct repo.
after tring yum install getting no package found error.
Please provide me some guidance to achieve this.
Related
From Zeppelin-0.7, Zeppelin started supporting Helium plugins/packages using Helium Framework. However, I am not able to view any of the plugin on Helium page (localhost:8080/#/helium). As per this JIRA, I placed sample Helium.json (available on s3) under /local-repo/helium-registry-cache. However, after that I got NPE while restarting Apache Zeppelin service.
I have tried Zeppelin 0.7 as well as Zeppelin 0.8.0 snaptshot versions. In particular, I want to use map Helium package - Helium-Map in Zeppelin note.
Can some one point me to any guide or documentation having detailed steps of using Helium package in Zeppelin? Any help would be greatly appreciated!
Zeppelin 0.7.x
Zeppelin 0.7.x doesn't support the online registry. In other words,
Zeppelin doesn't use helium.json. So you need to install each package by yourself.
clone the helium package what you want to install
modify the artifact value to the absolute path considering your local machine in helium-xxx.json
copy zeppelin-xxx.json into the $ZEPPELIN_HOME/helium directory (create if it doesn't exist yet)
restart Zeppelin and go to the localhost:8080/#/helium page, then install the package.
Zeppelin 0.8.0-SNAPSHOT
Zeppelin 0.8.0-SNAPSHOT supports the online registry. So you can install without any preparation.
But the NPE problem you've faced was fixed after https://github.com/apache/zeppelin/pull/2380.
So please git pull origin master and rebuild it :)
FYI, Now Zeppelin provides proxy functionality for helium. Refer https://github.com/apache/zeppelin/pull/2363
According to the MediaInfo ChangeLog, Amazon S3 support was added in v0.7.76 and even patched in v0.7.77 (latest).
However, I can't find any documentation on how to implement it. It's not in CLI help menu nor the SourceForge project pages. I was hoping someone here might have some insight as the SourceForge forum is closed off.
How do I craft a MediaInfo command to use Amazon S3 with Access Key & Secret Key? I'm using the CLI.
The closest thing I could find was someone's example Java code:
http://fossies.org/linux/MediaInfo_CLI/MediaInfoLib/Source/Example/HowToUse_Dll.JNA.java
It looks like they're crafting a custom HTTP request to S3 and streaming the response to MediaInfo. I'm not sure. I don't know Java; I only know Bash, Ruby, PHP.
Has anyone successfully got MediaInfo working with S3; something like this?
mediainfo https://AWSAccessKeyId:AWSSecretAccessKey#s3.amazonaws.com/bucketname/filename
Mediainfo executable can be built with libcurl on linux distribution using below commands: (I used centos)
yum groupinstall 'Development Tools'
yum install libcurl-devel
yum install wget
wget http://mediaarea.net/download/binary/mediainfo/17.12/MediaInfo_CLI_17.12_GNU_FromSource.tar.xz
tar xvf MediaInfo_CLI_17.12_GNU_FromSource.tar.xz
cd MediaInfo_CLI_GNU_FromSource/
./CLI_Compile.sh --with-libcurl
cd MediaInfo/Project/GNU/CLI
./mediainfo --version
Then following command will provide media information for Amazon S3 url.
mediainfo --Output=XML https://AWSAccessKeyId:AWSSecretAccessKey#s3.amazonaws.com/bucketname/filename
The above command won't work with AWS keys(filename) having special characters. By using pre-signed url, it is possible to use special characters in AWS Keys.
aws s3 presign 's3://bucketname/testing/mini & bar™©.mp4'
mediainfo 'presignd url'
The Java example is an example about how to download with Java and send data to MediaInfo from Memory. Now MediaInfo has native support of S3. So just provide this URL.
The only issue is that you must have libcurl available and MediaInfo compiled with libcurl support. This is not already available on all platforms (e.g. on Windows you must put libcurl.dll from libcurl website in the same folder as mediainfo).
Better delivery of such support (with libcurl provided directly, and fully tested, on all platforms) is planned but there is no ETA.
I face the same problem. Please try this, it will work
https://{yourAwsAccessKey}:{yourAwswsSecretKey}#{yourBucketName}.s3.awsamazon.com/{file_path_in_bucket}
I am trying to get a simple, single instance of RabbitMQ running via this RabbitMQ-chef recipe. Essentially, I have an Ubuntu machine, and I’d like Chef to take care of all the heavy lifting necessary to install, configure and get RabbitMQ running on it.
The documentation isn’t really written for beginners, but I went ahead and started by downloading the cookook:
knife cookbook site download rabbitmq
WARNING: No knife configuration file found
Downloading rabbitmq from the cookbooks site at version 4.1.2 to /Users/myuser/sandbox/chef/0.6.2/rabbitmq-4.1.2.tar.gz
Cookbook saved: /Users/myuser/sandbox/chef/0.6.2/rabbitmq-4.1.2.tar.gz
However now I’m at a complete loss as to what I need to script/configure in order to add this cookbook to my Chef server, such that when I SSH onto my target Ubuntu machine, I can bootstrap that machine with Chef and then run something to turn the Ubuntu machine into a RabbitMQ server. Any ideas?
I'm using an Amazon Linux EC2 instance and am wondering What AWS CLI tools are installed by default on it.
Is it just the EC2 CLI API tools? How can one tell? Also where is the preferred single location on an EC2 instance to install each of the various CLI tools (RDS, cloudwatch, etc.) if they aren't installed already?
If you might answer each of these questions I'd be greatly appreciative.
For the Amazon Linux AMI 2012.03, here's the list of installed packages.
To answer your question, here's the list of AWS tools:
aws-amitools-ec2-1.4.0.7
aws-apitools-as-1.0.61.0
aws-apitools-cfn-1.0.9
aws-apitools-common-1.1.0
aws-apitools-ec2-1.5.5.0
aws-apitools-elb-1.0.17.0
aws-apitools-iam-1.5.0
aws-apitools-mon-1.0.12.1
aws-apitools-rds-1.8.002
aws-cfn-bootstrap-1.1
aws-scripts-ses-2012.05.15
According to Amazon Linux AMI Basics:
to allow the installation of multiple versions of the API and AMI
tools, we have placed symlinks to the desired versions of these tools
in /opt/aws, as described here:
/opt/aws/bin—Symlink farm to /bin directories in each of the installed
tools directories.
/opt/aws/{apitools|amitools}—Products are installed in directories of
the form [name]-version and symlink [name] attached to the most
recently installed version.
/opt/aws/{apitools|amitools}/[name]/environment.sh—Used by
/etc/profile.d/aws-apitools-common.sh to set product-specific
environment variables (EC2_HOME, etc.).
There are no fixed standards or set rules about what is installed on AMIs in general.
Different Linux distros and different AMI publishers each decide what they want to put in their image and where.
In fact, an AMI doesn't even need to give you command line access to your instance through ssh if they don't want to.
If you have a specific AMI series in mind (Amazon Linux, Ubuntu 12.04 LTS from Canonical, CentOS 5.5 from RightScale) then update your question to include this.
For the record: the "minimal" variant of Amazon Linux does not have the full suite of CLI tools. Doing a yum install ec2-tools didn't get me what I wanted, so I just created a new instance with the non-minimal AMI. I also found that this minimal Linux isn't any more space-efficient, at least as originally configured; the additional 6 GB that would go to the root partition is left unallocated.
I am trying to install fuse via yum on our RHEL5 instance. Its not available in my yum list.
After checking, some sites suggests enabling rpmforge repo will provide the package in yum to install. I enabled rpmforge repo (latest for RHEL5), but there is no fuse in that as well.
I tried with EPEL repo as well, same result.
Can anyone help me to find the root cause of this?
Note: I can install fuse using src, but that is not working for the other software I am trying to install (s3fs), that's why I need the yum to get working so that I would have all the latest packages needed.
Thanks for the help.
-Noman A.
FUSE (kmod-fuse) has moved from RPMforge to ELRepo, since ELRepo focusses on hardware enablement for RHEL and derivative distributions (like CentOS or Scientific Linux).
http://elrepo.org/
Beware that in more recent releases of RHEL5, FUSE is part of the kernel.