Lumify: Not Launching Local Instance on Vagrant - yum

Followed the instructions to run a local instance of lumify using Vagrant.
Vagrant up demo, fails as the https://bits.lumify.io/yum/repodata/repomd.xml is down.
The try site is down as https://try.lumify.io/ as well.
Need pointers if any yum repo can be used for this.
I see that there are few dependencies related to opencv etc and i could not find them all in 1 place.
Any inputs on this would be greatly appreciated

I'm pretty sure active development of Lumify's open source version ended in 2015. Have you tried the open source version of Visallo? There's also an enterprise edition if you need additional capabilities or greater scalability.

Related

setting up monodevelop in xfce

I use this solution to have a VNC desktop session with a remote Ubuntu PC https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-vnc-on-ubuntu-16-04
I want to setup monodevelop on this machine. I followed the instructions and am able to run monodevelop and write code, however when I attempt to run it I get "Could not connect to the debugger". I tried various solutions suggesting changing environment variables to force monodevelop to use xterm and it did not work, however I'm not positive I did it correctly as the solution was meant for gnome and the modifications to the command for XFCE were not clear to me. At this point I'd be willing to get paid support, but I'm not even sure where I could find any for my use case. Does anyone have experience getting monodevelop to work on XFCE? If not what is the best environment for getting it going (ideally a way where I could remote in too). I'm very accustomed to the RDP workflow where I can actually troubleshoot on a development server and be very close to the real world environment to get things running, then check-in and deploy. I think there are a lot of platform differences with monodevelop so I really really really want to develop on Ubuntu (remotely).

Apache version 2.2 and security vulnerabilities

A penetration test has recently identified that one of our RHEL(6.7) servers running Apache 2.2.15 is vulnerable on a number of points and needs to be updated to the latest version 2.4. I have run yum update and it says that there are no packages marked for update. I understand that I will need to download the updates manually. There are a few questions I have around the requirement to upgrade Apache.
I am up to date on the 2.2 version tree. Does this mean that any security patches made to version 2.4 will be back patched to version 2.2.X as well?
I am running PHP (version 5.3.3) and MySQL (version 5.1.73) - will these be affected by upgrading the Apache version (Google tells me that there is no problem on both fronts - but I thought I'd ask before I started down this route).
If you experts tell me that I have no other choice but to upgrade, then I'm planning on using the instruction set here: https://unix.stackexchange.com/questions/138899/centos-install-using-yum-apache-2-4
Thank you in advance for your advice.
You could download the 2.4 source code from the Apache site and compile it. There's a setting which will configure for RedHat:
--enable-layout=RedHat
This setting will configure the paths for executables, configuration files, libraries etc in one go.
The following should be a reasonable starting point for a configuration line:
sh ./configure --enable-layout=RedHat --enable-mods-shared=all
then perform a make and make install
Do the same with a newer version of PHP (5.3.29 is available in the "old downloads" section, but try a newer version. Check the changes first though) and your problems should be lessened. Finally, MySQL or MariaDB is available for download and compilation too
Obviously, try all of this on a test machine first and back everything up. Your test machine should be as close as possible to your production machine. If you use something like VirtualBox to try it, you can take a snapshot at each point of the process and rollback if something goes wrong

How to install Mahout on Windows 8.1?

My goal is to build up a recommendation system and after going through many articles, I came across Mahout as a simple, yet effective way to go on. I already have XAMPP installed on my system.
How can I install Mahout? I need the complete instructions since I have neither worked with cygwin before, nor have I worked with Hadoop, and everywhere I see, I see these two mentioned very frequently. I first need to install it on my localhost before going on installing it on the server.
Here is a detailed instructions page to install Apache Mahout with Hadoop in windows. Its bit tedious, but can be done anyway.
http://alans.se/blog/2010/mahout-on-hadoop-in-cygwin/

Switch Vagrant to use Parallels instead of VirtualBox

Is it possible to use Parallels instead of (insane slow) VirtualBox in Vagrant?
Maybe this will help you (fresh and new)
https://github.com/yshahin/vagrant-parallels
While it's not Parallels (which you may have already paid for), there is a plugin for using VMWare Fusion:
http://www.vagrantup.com/vmware
The plugin is not free, so you'll need to buy licenses for both the plugin and Fusion.
I get a kernel panic in my VM a few times a week. According to Mitchell, VirtualBox has had kernel panic issues on Macs for years that have never been well resolved, and swapping to Fusion is the best alternative.
Finally there is an official Vagrant Provider from and for Parallels! Unfortunately it's not mentioned on www.vagrantup.com.
See Paralles' Vagrant Documentation and the Parallels GitHub page of the Vagrant provider project. For further questions about the provider there is a dedicated official forum.
As of now there is just one limitation: "The Parallels provider supports all basic Vagrant features, except the next: "Forwarded ports" configuration is not available yet." (taken from the readme on GitHub)
Thank you, AgentK, for pointing out that that "Forwarded ports" are available as of Parallels 10 for Mac.
There was a large commit a few month ago, that merged the machine-abstraction branch:
https://github.com/mitchellh/vagrant/commit/391dc392675c73518ebf04252d824fe916e8860b
which was even discussed a bit on Hacker News.
This branch brings in the "machine abstraction" code. This is a major
milestone in the development of Vagrant as it abstracts all of the
VirtualBox-specific code out into a plugin.
The gotcha:
White it is technically possible now to write plugins for other
providers, there is still major work to be done to make this feasible.
And as of now, the only provider in master is virtualbox:
https://github.com/mitchellh/vagrant/tree/master/plugins/providers
You can use Parallels with Vagrant. Here's a line by line set of instructions to do so (assumes you have Parallels and Vagrant installed).
$ vagrant plugin install vagrant-parallels
$ mkdir some-project/ && cd some-project
$ vagrant init parallels/ubuntu-14.04
$ vagrant up --provider parallels
Note, you only have to install vagrant-parallels once. Also note, you only have to pass in --provider parallels the first time you up, after that it will automatically use the parallels provider.
found this thread in google along with official Parallels-Vagrant integration: https://github.com/Parallels/vagrant-parallels

Automate CentOS installation with VMware for testing

Is is possible to automate the installation of an OS using VMware or any other virtualization product?
One of our products consists of a customized version of CentOS that installs the OS and our application on a server. It's much like any CentOS/RHEL installation where you choose a mode that corresponds to different kickstart options, and then you choose your keyboard type. The rest of the installation is automatic.
What I'd like to have is an automated system that will create a new guest VM, boot it with the ISO image of our product, start the installation (including choosing the keyboard), wait for the reboot, and then launch a set of automated tests.
I know that there are plenty of ways to automate the creation of new VM guests from existing templates/images, and I know you can use the VIX API to interact with virtual machines, but the VIX API seems to require that VMware tools is already running (which won't be the case when you're booting from the CentOS install disk).
This answer (Automating VMWare or VirtualPC) indicates that you can script VMware to boot from an ISO that does an unattended installation, but I would really like to test the same process that our customers will be using.
Another option might be to use Xen's fully-virtualized mode and see if scripting it over the serial port will work.
TIA,
Jason
I have a very very similar question, it is on superuser:
https://superuser.com/questions/36047/moving-vmware-os-image-as-primary-os-on-a-system
You can also use VirtualBox instead of VMWare. The VirtualBox SDK allows you to directly control the keyboard, the mouse the serial port and the parallel port of the guest without the virtualbox guest tools installed.
Unfortunately it doesn't offer a text console interface but the serial port can be connected to a local pipe file and that can probably be worked with just as well.
This may not be exactly what you need:
I have done something similar with a Ubuntu-based install. We used preseeding (Debian's form of kickstart), to answer all the questions during the install - providing the preseed file and the installer via tftp.
In addition to the official Ubuntu mirror we added the apt-server with our own packages in the preseed file. We put a .deb version of vmware-tools on the apt-server and added it to the packages to be installed.
The .deb of vmware tools just contained the .tar.gz and a postinstall script that would extract it to /tmp and run the vmware install script (which has a switch to be run unnattended, so it does not ask any questions).
So after the reboot vmware-tools were up and running and we could use vix to script the rest (which was not very reliable).
If you should encounter problems with running vmware-config.pl during boot, you could make a custom package that just extracts the tools and an init script that installs them on first boot, disables itself and reboots.
Maybe you can use this strategy (replacing apt by yum, preseed by kickstart and tftp by a remastered iso). If you really need to test that your users choose a keyboard in the installer (which is not very different from kickstart) this would obviously not work for you..