Evening Tim,
There is no impact, we are keeping the solaris kit. Plus they have lots of
other stuff to deal with too. For other things. Oracle included.
Really your time line, I'm older than I look in type! I lived through the
mainframe years, first as a Cobol developer, then Tech Support for mainframe
and operating system as well as doing system programming. ICL 1900/2900/3900
series. Things change all the time, I changed too. Got into IDMSX databases.
Moved to oracle and firebird. Started my own company in 2003 with my wife.
Worked pretty solid ever since.
Been through the Web stuff, didn't like it then, don't like it now. Cloud? It's
just another "big thing" until the next one comes along. Remember Citrix? I do
too. It was and is pretty dire. Other opinions might be available of course.
How does cloud affect me? I take longer to log in to the servers than I used
to, and it's windows rather than some form of Unix, so I adapted, wrote oraenv
and other useful things that I'm used to in the *nix side, and got on with my
job.
I agree that cloud is sort of useful, with pay as you go everything, but oracle
and or Microsoft shafted a lot of people when the old pay as you go oracle
licencing was dropped, once customers had buy in of course, now the licencing
is a lot more complicated. When we turn the cpus up to 40 cores, or whatever,
for a couple of days, how the hell do we licence that? Not my department,
thankfully!
The next think along will be what it is. Where am I placed? I'll adapt, or I
won't bother with it. I have a choice. I contract so I'm not stuck in one place
for the rest of my life. The next big thing might interest me, in which case
I'll buy training and try for contracts, if it doesn't, I won't.
As for hardware, not my department, I'm not involved. That's an SEP.
Cheers,
Norm.
PS. SEP = Someone Else's Problem. (Douglas Adams)
On 17 December 2016 18:15:30 GMT+00:00, Tim Gorman <tim.evdbt@xxxxxxxxx> wrote:
No, there *is* indeed something to see there, as it is an example of an
IaaS migration. Here is a question to ponder: What is the impact of
this migration on the SysAdmin team?
IaaS migrations are transitional, for both parties (i.e. cloud
provider,
cloud customer). Cloud providers are scaling up and improving their
services, transitioning from leading-edge to mainstream and enterprise.
Cloud customers are testing, often committing.
I think the present and near future holds a lot of transitional "hybrid
data centers", with production remaining on-premises until the current
leases expire or the current purchases amortize, and
development/testing
and other non-production systems leading the charge to IaaS. In a few
years, after non-production systems secure the beach-head in IaaS,
production systems might follow the established migration path, or they
might evolve directly into SaaS migrations by then.
If past history is any guide, consider these rough facts...
The first wave of mainframe-based commercial deployments covered about
25-30 years, from the 1960s to the 1980s. After the advent of desktops
and departmental computing in the 1980s, client-server computing gained
momentum in the 1990s, over a period of period of perhaps 8-10 years.
Web-based 3-tier architectures came to dominate on-premise in the
2000s,
and then co-location and/or hosting of these architectures arose in the
2010 timeframe. The problem with co-location/hosting services is that
it is continues just-in-time, budgeted provisioning of compute and
storage (i.e. slow).
In the late 2000s, AWS was experimental, but in the past 5 years, IaaS
services have begun to dominate. The main difference between
co-location/hosting and IaaS is instant provisioning and pay-as-you-go
pricing (i.e. agility).
So ask yourself: What is next along this continuum? When? And where
am I positioned?
More practically: When do current hardware leases expire? Or
amortize?
----------
From a personal standpoint, after a really painful experience with a
startup going out of business in 1988-89, I made four career
resolutions
by 1990...
1. never work where technology isn't the product
2. nothing good happens after 5pm
3. data is the only thing with value
4. pursue a technical, not managerial, career path
The first meant that I would never again be a "cost" to the business, I
would "be" the business. The second meant that I wouldn't work for
poorly-run or "evil" companies; consistent demands for long workdays
are
a leading indicator of company failure. The third led me away from
application development and toward databases. The fourth has kept me
happier, if less upwardly mobile.
Like the US constitution, I've made amendments along the way, but so
far
it has been useful.
On 12/17/16 02:24, Norman Dunbar wrote:
For what it's worth, my current contract is a migration from Solaris
to Microsoft Azure cloud.
Once I'm done with that, the permanent DBAs are staying on and taking
care of it all. It's "just" a server really. In this case anyway, but
a server you can "turn up to 11" for some stuff and back down again
for other stuff.
Nothing to see here!
Cheers,
Norm.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
