Google Cloud installed software through Google Cloud Launcher seems not to have a simple defined update or upgrade process. New customers are offered latest versions of software (Debian 9, Apache 2.4.25, Open JDK 1.8.0 etc.) but we old ones are not being guided about how to upgrade to those new versions. We, old customers, seem condemned to have additional resources to search, evaluate, test and deploy new versions of the software deployed by Google Cloud Launcher, or stay with the old most inefficient and probably unsafe software version (Debian 7, Apache 2.2, JDK 1.7.0 etc.). But there is another option: Migrate to Amazon Elastic Compute Cloud where upgrading software is supported: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/managing-software.html. Amazon Web Services does update the repositories: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/add-repositories.html and of course, provides a process to update the installed software. Does Google Cloud offer an upgrading process or is planning anything in that direction, or should we users low in resources plan to move to Amazon Cloud?
Related
Similar to the Windows question, Github workflows on MacOS VM offers PostgreSQL, but it does not include PostGIS. I would like to install it, but it is missing as an installable package. How can I use PostGIS in my CI?
Restarting a topic I found here, a few years back: need to migrate a large pool of NFS shares / mount points content, used equally by Windows and Linux clients, from on-prem, to AWS. I looked at the official EFS page # AWS, here, and there still doesn't seem to provide "support" for Windows instances. On the other hand, as few mentioned a few years back the UMIch NFS client ver 4.1 for Windows, that is already [what I assume to be] a new version available officially from Microsoft, supporting Server 2012, 2016, etc. Is Microsoft client still lacking what the UMich client offers, in order to work with the AWS EFS?
I am new to ruby and just beginning to understand It's potential. So I am trying to use it for my everyday tasks. One of those things would be the setup of a Webservice on a local machine for testing. It set up script should:
check out several projects from subversion repositories
install Hadoop (if it's not already installed), start the Server and execute a few commands in the hbase shell
install the JDK (if not installed)
install MySQL (if not installed) and execute some SQL to create and set up the DB
Install maven (if not installed) and run some maven tasks.
So here's the deal. I want this to be a cross platform installer - it should be able to install the Webservice on Windows, Linux or OsX.
Is it possible to implement this in Ruby and what gems could be useful for that task? Are there better ways to create such an installation routine?
Regards
R.
Have a look at Chef. It provides an automation framework for managing systems. It's written in Ruby and you use a mostly Ruby recipe DSL.
People package Cookbooks for managing groups of installation and configuration recipes, which are normally based around a piece of software.
Hadoop
MySQL
Maven
Java
You will run into issues bridging the gap between Windows and Unix. Although Chef does provide good Windows support these days most Chef/community cookbooks will support Linux primarily as they can rely on the underlying package manager which Windows lacks. Often you may end up finding/using separate Windows cookbooks specifically for the Windows install.
For when you do need to do a Windows install, look at using Chocolatey and it's cookbook which provides a unix like package interface for Windows so you don't need to worry about packaging up the software manually or dealing with random NSIS/MSI installer options.
If you do extend one of the Unix cookbooks to support Windows, be nice and contribute it back to the community.
I develop a windows software with Lazarus/free pascal. this is a simple hotel accounting software.
I am using Mysql 5.5. I have googled for cloud storage to use in my application. I select goolge app engine cloud sql. Now I have a question that will it work or not?
Yes, you can whitelist IP addresses you want to be able to connect to your Cloud SQL instance. See this article for more information.
We want to have scalable Reporting services. And we need to install Custom Rendering Extensions on this scalable Reporting Services. This is the main requirement for us. SQL Azure Reporting doesn't suite the requirements, because it is impossible to extend this service with custom rendering extension. We had an idea to install Reporting Services on each instance separated from SQL Azure and Azure Reporting, but Rendering Extensibility is not available in free editions of SQL Server and it costs too much to use paid edition. The database of these reporting services instances will be stored in SQL Azure and we will be able to leverage scalable Reporting Services tool with the required rendering extension. The problem is price, complexity and no benefits from SQL Azure Reporting. So, we got stuck with Microsoft clouds. And don't see any reasonable solution with Microsoft clouds.
So we considered Reporting Services on EC2 as they have special cloud license. And we are not quite sure whether it is possible to achieve what we need or not.
We've found that it's possible to install SQL Server2008R2 on EC2 so that the data of the database will be stored in EBS which is available to all the instances. So we have scalable Reporting Services in that case.
The question is lying in the Amazon Virtual Images:
We suppose that we need to install predefined configuration with Windows OS and SQL Server 2008R2 and we wonder if it (1) includes Reporting Services, (2)is it possible to install some more software on this predefined virtual machine (rendering extension), (3)is it possible to organize such scalable Reporting Services with Custom Rendering extensions and to leverage load balancing and etc.?
You don't have to use the AWS provided SQL Server 2008 R2 AMI if you don't want to.
If you bring your own licenses, you could go with a base EC2 install, and then install whatever software you want over the top of it.
ie - install the Windows AMI, and then run the SQL Server installation of your choice. The second step then is to install any additional extensions you require.
I would also recommend that once you complete the installation that you create an AMI of it so that you can repeat the installation at a later date.