Cut Over to New Data Center and Upgraded OS Done. :) Post: 303022893

Sponsored Content

The Lounge What is on Your Mind? Cut Over to New Data Center and Upgraded OS Done. :) Post 303022893 by Neo on Sunday 9th of September 2018 01:38:21 AM

09-09-2018

Administrator

Quote:

Originally Posted by Aia

I would like to repeat that it is all about CI/CD ( I do not have to highlight it since I made myself clear before). Companies (customers) that do not implement CI/CD for the most part do not appreciate the evolution to the Cloud. Thanks to Cloud computing and the implementation of automation the speed of developing and delivering time for applications is faster. I enjoy engineering systems that almost do not require manual intervention from the moment that we commit code to source control.
I have enjoyed seen teams confidence raise by the nature of CI, knowing that tests are well crafted, and real to what it will show in production. That a whole piece of infrastructure is created at demand, automatically for CI and once that the fast feedback is reported, it is brought down until the next test, which it could be some few minutes later. This is not a buzzword, it is real results that benefits organizations that wants faster deployments without compromising quality assurance and I have the fortune to work doing that. There is pride in me when I know I have engineered a system that provides reproducible results and that has been committed to source control and that can be brought to life in several minutes.
In fact, with the utilization of containers now I can even provide quicker infrastructure where immutability is possible.
It is not my intention to convince anyone (I am not in that business) but I want to reintegrate my original statement.

That's all great, and well written, but it has little to do with UNIX.COM moving our legacy server over to a new data center and upgrading.

If I moved it to the cloud, I would consider that a downgrade, not an upgrade, LOL

We have been on the cloud before... it's not an upgrade for UNIX.COM and our server.

Moving UNIX.COM to "the cloud" would be a downgrade, at least based on my experience.

And in closing moving to the cloud would not provide UNIX.COM:

Quote:

Continuous Integration and Continuous Delivery and Continuous Deployment.

This I know as a fact from years of experience.
Cheers.

This User Gave Thanks to Neo For This Post:

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

5 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

Cloud Enabling Computing for the Next Generation Data Center

Hear how the changing needs of massive scale-out computing is driving a transfomation in technology and learn how HP is supporting this new evolution of the web. More...

2. HP-UX

Need to set up a HP cluster system in a data center

What are the server requirements, Software requirements, Network requirements etc, Please help me.. as 'm new 'm unable to get things done @ my end alone. Please refrain from typing subjects completely in upper case letters to get more attention, ty.

3. Shell Programming and Scripting

Failure rate of a node / Data center

Hi, Please, i have a history of the state of each node in my data center. an history about the failure of my cluster (UN: node up, DN: node down). Here is some lines of the history: 08:51:36 UN 127.0.0.1 08:51:36 UN 127.0.0.2 08:51:36 UN 127.0.0.3 08:53:50 DN 127.0.0.1 ...

4. What is on Your Mind?

Resolved: Issue in Server Data Center

Dear All, There was a problem in the data center data, which caused the server to be unreachable for about an hour. Server logs show the server did not crash or go down. Hence, I assume there was a networking issue at the data center. Still waiting for final word on what happened. ...

5. What is on Your Mind?

OUTAGE: Data Center Problem Resolved.

There was a problem with our data center today, creating a site outage (server unreachable). That problem has been resolved. Basically, it seems to have been a socially engineered denial-of-service attack against UNIX.com; which I stopped as soon as I found out what the problem was. Total...

LEARN ABOUT LINUX

relup

relup(5)							       Files								  relup(5)

NAME

       relup - Release upgrade file

DESCRIPTION

       The release upgrade file describes how a release is upgraded in a running system.

       This file is automatically generated by systools:make_relup/3,4 , using a release resource file ( .rel ), application resource files ( .app
       ) and application upgrade files ( .appup ) as input.

FILE SYNTAX

       In a target system, the release upgrade file should be located in the OTP_ROOT/erts-EVsn/Vsn directory.

       The relup file contains one single Erlang term, which defines the instructions used to upgrade the release. The file has the following syn-
       tax:

       {Vsn,
	 [{UpFromVsn, Descr, Instructions}, ...],
	 [{DownToVsn, Descr, Instructions}, ...]}.

	 * Vsn = string() is the current version of the release.

	 * UpFromVsn = string() is an earlier version of the release to upgrade from.

	 * Descr  =  term()  is  a user defined parameter passed from the systools:make_relup/3,4 function. It will be used in the return value of
	   release_handler:install_release/1,2 .

	 * Instructions is a list of low-level release upgrade instructions, see appup(5) .

	   It consists of the release upgrade instructions from the respective application upgrade files (high-level instructions  are	translated
	   to low-level instructions), in the same order as in the start script.

	 * DownToVsn = string() is an earlier version of the release to downgrade to.

       When  upgrading	from  UpFromVsn  with  release_handler:install_release/1,2  ,  there  does  not have to be an exact match of versions, but
       UpFromVsn can be a sub-string of the current release version.

SEE ALSO

       app(5), appup(5), rel(5), release_handler(3erl), systools(3erl)

Ericsson AB							   sasl 2.1.9.3 							  relup(5)