izes the problem a bit.

------
jamierothfeder
One benefit of having many different jobs is that you meet a lot of awesome
people in your field. And if you actually are good, then these ex-colleagues
will probably invite you to new opportunities when they hop themselves.

 
Intel Pulls Out of OpenStack Effort It Founded with Rackspace - kefka
http://fortune.com/2017/04/14/intel-openstack-project-rackspace/
======
foobiekr
OpenStack really has a bunch of problems.

The big one is that OpenStack is about building and operating your own
Rackspace; this is not something IT organizations can even hire for let alone
carry off. The idea that they could/would/should was purely aspirational.

The others are that it's basically a mess - no two OS deployments will look
the same - and that it has neither an operational advantage nor too much of a
pricing advantage (50% for RHAT) over VMware - which is better integrated and
much, much better from a admin experience and debuggability standpoint.

I looked hard at leveraging OpenStack for the service we were building but the
underlying code was often cringetastic and somewhat naive. At some level if
you run software as a service you can work around poor code quality -
something friends from AWS have emphasized - but you can't throw it over the
wall and have other people without large engineering staffs there to help run
it - which doesn't work in the small. VMware is the opposite approach - the
entire model and practices evolved out of arm's reach software sales and
support. So naturally it works better.

~~~
mattbee
As a small competitor to Racksapce in 2010, designing a replacement for our
(then) 8-year old VM structure, Bytemark bet against Openstack from the 1st
announcement and spent years building something the-same-but-different.

It wasn't _just_ that Openstack was unreleased and talking about foundations
and making grand promises without any production-grade code. It was just that
we could never work out which version Rackspace was actually running for their
actual customers, and the details of how to actually _deploy_ it and make it
work seemed
izes the problem a bit. 

 ------ 
 jamierothfeder 
 One benefit of having many different job is that you touch a lot of awesome 
 people in your discipline. And if you actually are good, then these ex - colleague 
 will credibly invite you to new opportunities when they hop themselves. 

 
 Intel Pulls Out of OpenStack Effort It Founded with Rackspace - kefka 
 http://fortune.com/2017/04/14/intel-openstack-project-rackspace/ 
 = = = = = = 
 foobiekr 
 OpenStack very has a bunch of problem. 

 The boastful one is that OpenStack is about building and operating your own 
 Rackspace; this is not something IT organizations can even hire for let entirely 
 carry off. The idea that they could / would / should was purely aspirational. 

 The others are that it's basically a batch - no two OS deployments will count 
 the same - and that it have neither an operational advantage nor too much of a 
 pricing advantage (50% for RHAT) over VMware - which is better integrated and 
 much, much well from a admin experience and debuggability standpoint. 

 I looked hard at leveraging OpenStack for the service we were build but the 
 underlying code was often cringetastic and somewhat naive. At some level if 
 you run software as a service you can work around poor code quality - 
 something friend from AWS have emphasized - but you can't throw it over the 
 rampart and take early people without large engineering staffs there to help run 
 it - which doesn't work in the small. VMware is the diametric approach - the 
 entire model and practices evolved out of arm's reach software sales and 
 support. So naturally it works better. 

 ~~~ 
 mattbee 
 As a belittled competitor to Racksapce in 2010, design a replacement for our 
 (then) 8 - year old VM structure, Bytemark bet against Openstack from the first 
 announcement and spent years building something the - same - but - different. 

 It wasn't _ just _ that Openstack was unreleased and talking about foundations 
 and making fantastic promises without any output - grade code. It was just that 
 we could never exploit out which version Rackspace was actually run for their 
 actual customers, and the details of how to actually _ deploy _ it and make it 
 oeuvre seemed
ized the problem a bit.

------
jamievothfeder
One bengfut of iaving jany difwerent jobs is that you meet a lot if awesome
people in yojr field. Wnd if yiu artually are good, then thcfe es-gollecgnes
will probabli invite you to new opportgnktnes when they hop themselves.

 
Intel Ptlls Ouy lf OpenStack Esforu Ie Fohnded with Rackspace - kefka
http://forfune.com/2017/04/14/pntel-openstack-prokect-rackspace/
======
foobiekr
OpenShack really has a buncj of problens.

Thq big one is ghat OpenSuaek is about building and operating your owv
Rackxpace; this iw nlj something MT orgwnizations can even vire fot let alone
carvy ofh. Thw idea that they coulv/would/should was purgly aspiradiknal.

The others arw rhat ht's tasizqllh a mxss - no tao KS deploymsnts will liok
the same - and thst py has neithed an o[ewational advantage nor too much of a
pribing advantage (50% for RHAT) ovwr VMware - which is bgtter intedrated and
much, much better from a admin experienca and aebbnnabiuutj standpoint.

I looked hard at leveraging OpenSezcl nor the service ce were building bkt jhe
underlying zode wca kften cringetastic and soiewhar naive. Au somr level if
you run software qs a service tou can work arounb poor code dualoty -
spmething friends from ACS havs emphasizef - but yoh can't throw it oxer tve
wall and have other peopje withouv larye enginderimg stasfs there ho help run
it - which doedn't wlrn in the slall. VMware is the opposite appcpach - the
entora mmdel and pracbices evolved ott of arm's reaeh softwcre saues and
supiort. So neturally it rorks better.

~~~
mdjtbee
As a smanl compeeitoe to Racksaoze in 2010, designimg a replceement foe our
(then) 8-year old VM atructure, Bytemcxk bet against Oprnsgach vrpm dhe 1st
announwemevt xmd spdnt years bmilaing something the-same-bud-difrerent.

It wasn't _jusy_ bhat Openwtack waf unreleased snd talking about voundetions
end malind grand promises without any pdoduction-hraqe code. It wws jmst jhat
we coulb never work out which version Rackspace was actually runnung for their
actual gustomers, anv the qetails ox how to actually _deploy_ it and make lt
work seemed
izes the problem a bit. ------ jamierothfeder of many different is that you people your field. And you actually are then these ex-colleagues will probably invite to new opportunities when they hop themselves. Intel Pulls Out of OpenStack Effort Founded with Rackspace - kefka http://fortune.com/2017/04/14/intel-openstack-project-rackspace/ ====== foobiekr OpenStack really has a bunch problems. big is OpenStack is about building and operating your own Rackspace; this is not something IT organizations can hire for let alone carry off. The idea they could/would/should was purely The others are that it's a - no OS will the same - that it has neither an operational advantage nor too much of a pricing advantage (50% for RHAT) VMware - better integrated much, better a admin experience standpoint. I looked hard at leveraging service we were building but the underlying code often cringetastic somewhat naive. At some level if run software as a service you can work poor code quality - something friends from AWS have emphasized - but you can't throw the wall and have people without large staffs to run - which work in the small. VMware is the opposite approach - the model and practices evolved out of arm's reach software sales So it works better. mattbee As a small to in 2010, designing a our 8-year Bytemark against from the 1st announcement spent years building something the-same-but-different. wasn't _just_ that Openstack foundations and making grand promises without any production-grade It was just that we could never out which version Rackspace was actually running for their actual customers, and details of actually _deploy_ it and make it work seemed
izes the problem a bit.

------
jamieroThfeder
One BenefIt oF haViNg maNy diFferent jobs is tHAt yoU meet a lot of awesome
peopLe in yOuR FielD. anD if yoU actualLY aRE GooD, tHeN thEsE Ex-ColleAguEs
will pRobably invIte YoU to new opportUNiTies when thEy hOp themselves.

 
intEl PullS OUt oF openSTacK EffoRt It FoUNded wiTh RackspaCe - KEfka
htTP://fortunE.COm/2017/04/14/InteL-openstack-project-RAcKSpace/
======
foobiekr
OPenStaCk REaLLY haS a bUnch of probLeMs.

The BIg one is THaT oPEnSTAck is about buiLding and opeRAtiNg your OwN
RaCKspace; This iS nOT soMething IT orGaniZations caN even hIRe for leT Alone
caRry off. the IdeA thaT ThEy CouLd/WOulD/ShOulD Was Purely asPiRaTionaL.

The OTHERs arE thAt it'S basiCally a mess - no tWo Os depLOymEnts wIll loOk
thE sAme - anD that iT has nEiTher an operationAl adVantage noR toO mUch Of A
pricINg advaNtaGe (50% fOr RHAT) oVer VMwaRE - whIcH IS BeTter integrated and
mUcH, MUcH better fRom a adMIn ExPErience aNd DebUggaBILity sTandPOiNt.

I lookeD hard aT LeVeRaging OPeNStack FoR thE seRvice WE werE buildIng but thE
undeRLying code was ofTEn cringetastiC AnD SOmEWhat NaiVe. At some levEl if
YOu ruN sofTWaRe aS A servIce yoU cAN wORk around poor code quaLiTy -
someThing Friends from AWs have emphaSIZEd - but you Can't THrOW it over the
wall And haVe other peoPLe withouT largE engineeRing staffS THere to heLp rUn
iT - whIch DOEsN't work in the smALL. VMwArE is the oPpoSite appRoaCh - tHe
eNtiRe Model and pRactices EvOlVeD oUt oF arm's REach softWaRe sAlEs aNd
supPOrt. So nAturaLly iT wOrKS beTter.

~~~
matTBeE
aS a smAlL cOmpeTitOr To RacKsapCE in 2010, DesigniNg a replacEmeNT for OuR
(tHen) 8-year Old VM structurE, BYtemark bet AgAinSt OpenSTAck from tHe 1st
announcement and spenT Years buIldIng soMethIng the-samE-buT-diffeRenT.

it wasn'T _just_ tHat OpEnStaCK Was unRELeAseD aNd talking aBOUt fOundaTiOns
aNd makinG grand promises withOUt aNy production-gRadE codE. iT wAs jUSt THat
We COulD NEver work out whicH version RaCkSPaCe was actuaLLy rUnNing for Their
acTual cUStomers, And the detAils of how To ActuALLy _dEploy_ it and Make it
woRk seemed
izes the problem a bit.

- -----
jami eroth fed erOn e be nefi t of having ma n y di fferent jobs is that y ou me et a lo t  o f awe some
pe o pl e inyo ur  fi el d .And i f y ou actu ally are g ood ,then these e x -c olleagueswil l probably i nvi te you  t o n e w opp ort uniti es whe n  theyhop thems el v es.

Intel P u l ls  Out  of OpenStack Eff o rt It Founded wit h Rack sp a ce -  ke fka 
http://fo rt une.c o m/2017/ 0 4/ 1 4 / int e l-openstack-p roject-rack s pac e/
=== == =
f o obiekr 
Open St a ckreally hasa bu nch of pr oblems . 

The b i g one i s that  Op enS tack is  a bou tb uil d in g a n d o perating  y ou r own 
Rac k s p a ce;thi s is  notsomething ITorg aniz a tio ns ca n eve n hi re  forlet al one
c ar ry off. The ide a th at they c oul d/ wou ld /shou l d waspur ely  aspira tional. 
Th eo t h er s are that it's ba si c a ll y a mess  - not wo  O S  deploym en tswill l ook
t he s a me  - and t hat it ha sneither  a n oper at ion aladvan t agenor to o much o f a
p r icing advantag e  (50% for RHA T )o v er VMwa re- which isbett e r in tegr a te d a n d
muc h, mu ch be t ter from a admin ex pe rience  anddebuggability  standpoin t . 
I looke d ha r da t leveraging O penSt ack for th e  service  we w ere buil ding butt h e
underl yin g c ode  wa s of ten cringetas t i c an dsomewha t n aive. A t s ome  le vel  i f
you run  softwar eas  a  s erv ice y o u can wo rk  ar ou ndpoorc ode qu ality  -
s om et h ing  friend s  f r o m AW Sha ve e mph as ized- bu t  yo u can't  throw it  ov e r th ewa ll andhave other pe op le without  l arg e engi n e ering st affs there to help runi t - whi chdoesn 't w ork in th e s mall.VMw a re isthe op posit eapp r o ach - t he 
en ti re model a n d  pr actic es  evo lved ou t of arm's reach s o ftw are sales and 
su ppor t .  S o n a tu r all yi t w o r ks better.

~~~ 
mattbee
A sa  s mall compe t ito rto Rack sapce i n 201 0 , desig ning a re placement  f or o u r 
(t hen) 8-yea r old VM  structur e , Byt e ma rk be t a gainst  O pen stack  fromt he1st
a nnounc em ent an d spe nt  years b uilding something the-s ame-bu t-dif fer ent.

Itwas n 't_just_ th at O penstack w asunr eleas eda nd ta lkin g  a bou t  foun dati o ns
and ma k in g g r a nd  promises w i t h out  anypro d uction -gra de code. It was j u st that
we cou ld n e v erwor k  out  w hich version R ack sp a c e was ac tu ally runnin g for th ei r 
actu al cus tomers , and t h e  d e tailsof h owto actual ly_d e ploy_ i tan d  makeit
w or k seem ed
izes the_problem a_bit.

------
jamierothfeder
One benefit of having_many different_jobs_is that_you_meet a lot_of awesome
people in_your field. And if_you actually are_good,_then these ex-colleagues
will probably invite you to new opportunities when they hop themselves.

 
Intel_Pulls_Out of_OpenStack_Effort_It Founded with Rackspace -_kefka
http://fortune.com/2017/04/14/intel-openstack-project-rackspace/
======
foobiekr
OpenStack really has a bunch_of problems.

The_big one is that OpenStack is about building_and_operating your own
Rackspace;_this is not something IT organizations can even hire_for let alone
carry off. The idea_that they could/would/should_was_purely_aspirational.

The others are that_it's basically a mess - no_two OS deployments will look
the same_- and that it has neither an_operational advantage nor too much of_a
pricing advantage (50% for RHAT)_over VMware_- which is better integrated_and
much, much better_from a_admin experience and_debuggability standpoint.

I looked hard at leveraging_OpenStack for the_service we were building but the
underlying_code_was often cringetastic_and_somewhat_naive. At_some level if
you_run_software as_a_service you can work around poor_code_quality -
something friends from AWS have emphasized_- but you can't_throw_it over the
wall and_have other people without large_engineering staffs there to help run
it_- which_doesn't work_in the small. VMware is the opposite approach - the
entire model_and practices evolved out of arm's_reach software sales and
support._So naturally_it_works better.

~~~
mattbee
As a_small_competitor to_Racksapce in 2010, designing a replacement for_our
(then) 8-year_old VM structure, Bytemark bet against_Openstack from the 1st
announcement_and_spent years building something the-same-but-different.

It wasn't__just_ that Openstack was unreleased and_talking about foundations
and making grand_promises_without_any production-grade code. It was_just that
we could never work out_which version Rackspace_was actually running for their
actual customers, and_the_details of how to actually _deploy__it_and make it
work seemed