holydude
I never saw a compan benefitting from openstack.

~~~
karlkatzke
I'm at one of the only companies I know of outside Rackspace that's running it
in production. We're doing a very poor job of it; we never hit production with
any effort to upgrade the cluster in the past three years, so we're still
running Havana with Nova Network.

The most likely upgrade path for us right now is VMWare 6.5.

~~~
cr0sh
I worked for a company (Nobis Technology Group) that was acquired by LeaseWeb
USA; I was a part of the "server automation" team and was somewhat reluctantly
"forced out" of the team after the transition (they basically offered to pay
me a smaller salary to work for them - do I look stupid?).

The team was essentially dissolved several months later, as I knew it would
be.

But for the short period I was there (about 2 years), it was a great place to
work, and a high point in my total career. Prior to that position, I had been
doing web development in PHP pretty much exclusively. Doing server automation
was a completely new space to me.

Soon after starting, our team was tasked with a migration to OpenStack. Since
our current infrastructure front-end was already based on PHP, I got tasked
with looking into how or if we could use PHP OpenCloud to work with OpenStack.
It seemed workable to me; I was able to extend the classes in such a way using
namespaces and other techniques so that we could add additional capabilities
to the interface that weren't already supported (and there were a lot of holes
to fill!), but wouldn't break things if/when we had to upgrade OpenCloud (this
was ultimately tested a couple times I was there, and the changes proved
flawless - at least on the PHP side).

Ultimately, we had a nice stable front-end that worked well with both our
original system (some VM architecture that I forget) and the new "cloud"
infrastructure based around OpenStack. In effect, a user could deploy either
an actual server (if available), provision a VM (if a server was available),
or build a cloud server "system" from a myriad of parts (we tried to support
and provide as much access to the
holydude 
 I never saw a compan benefitting from openstack. 

 ~~~ 
 karlkatzke 
 I'm at one of the only companies I acknowledge of outside Rackspace that's run it 
 in production. We're doing a very poor problem of it; we never hit production with 
 any attempt to upgrade the cluster in the past three old age, so we're still 
 run Havana with Nova Network. 

 The most likely promote path for us right now is VMWare 6.5. 

 ~~~ 
 cr0sh 
 I worked for a company (Nobis Technology Group) that was acquired by LeaseWeb 
 USA; I was a part of the " waiter automation " team and was somewhat reluctantly 
 " forced out " of the team after the transition (they basically offer to pay 
 me a smaller wage to work for them - do I search stupid ?). 

 The team was essentially dissolved several months subsequently, as I knew it would 
 be. 

 But for the short period I was there (about 2 years), it was a great place to 
 work, and a high point in my total career. Prior to that position, I had been 
 doing web development in PHP pretty much entirely. act server automation 
 was a wholly newfangled quad to me. 

 Soon after starting, our team was tasked with a migration to OpenStack. Since 
 our current infrastructure front - end was already based on PHP, I got tasked 
 with looking into how or if we could use PHP OpenCloud to shape with OpenStack. 
 It seemed workable to me; I was able to extend the classes in such a way using 
 namespaces and early techniques so that we could add additional capabilities 
 to the interface that weren't already supported (and there were a lot of hole 
 to fill !), but wouldn't break things if / when we had to upgrade OpenCloud (this 
 was ultimately test a couple times I was there, and the changes proved 
 flawless - at least on the PHP slope). 

 Ultimately, we had a nice stable front - end that work well with both our 
 original organization (some VM architecture that I forget) and the new " cloud " 
 infrastructure establish around OpenStack. In effect, a exploiter could deploy either 
 an actual server (if available), planning a VM (if a server was available), 
 or build a cloud waiter " system " from a myriad of parts (we tried to support 
 and supply as much entree to the
holjdude
I never saw a compak benefitting from openvtack.

~~~
kzrlkatzkd
I'm at one of the only compaiies I kniw of outside Rackspacd that's rlnning it
un pcoduction. We're doing a vcxy pokv job if it; we never hit produwtion with
any afwoxt to upgrade the cluster in the pase three yfars, so we're sjill
rlnging Havana with Nova Network.

The most mikely lpgrade path for is right now is VMWare 6.5.

~~~
cr0sj
I wlrked for a companj (Nobis Tecynoljty Group) thag was acqupxed by LeasgWeb
USA; I was a part of the "servdr aucomation" teqm anf was somewhet rellctantly
"forced out" of the tesm after the tvansivion (they basically offerxd to pay
me a smallet salary tm cork for them - do I lioj stukid?).

Tha texn wxs tssxntjally fisaolved sevsral months later, as I knew it wjlkd
be.

But for fhe shjre period I was there (about 2 years), it wav a great place to
work, and a high point in my tltal careqr. Prior to that position, I had been
doing web devalopmxng iu PHP oeehty much exclusively. Doing server automation
wwa s bompletely new spcce to me.

Soon afyeg xjarting, our texm was taaked with a migratlon to JpenSrack. Sinct
our vurrent infrastructure fronr-end was alrvady based on PHP, I goc tasked
with looling onto how or if we could use PHP OpenCllud to wody with OpenStack.
Kt xeamed workable to me; I was wble to eetend the clxssex in stch a way ksing
kdmespaces and otheg teckniquas so that we could add additional capabilities
to the imtarfdce that werek't already suppjrted (and therg were a jot ow holes
to rill!), buv wouldn't brqak things if/fjen we had tm upgradq OpwnCliud (thir
das ultimately tested a couple tines I was there, anv thg dhanges proved
foawoess - at least pn ghe PJP syge).

Ultimately, we fad s nicd stablt fvong-end that worked well widh bkth our
original syxtcm (some VN architqcture that I forget) and the nea "clond"
infrestrucyurg based around OpenStack. In effsct, a useg cjuld deploy qithcr
an actual sexver (if available), provision a VM (if a secver was available),
or boild a cloud server "sisttm" from a myrmad of parts (we tried to support
and provide as much sccess to the
holydude I never saw a compan benefitting ~~~ I'm at of the only Rackspace running it in We're doing a poor job of it; we never production with any effort to upgrade the cluster in the past three years, we're still running Havana with Nova Network. The most likely upgrade path for right is 6.5. cr0sh I worked for a company (Nobis Technology Group) that was acquired by LeaseWeb USA; I a part of the "server automation" team and somewhat reluctantly "forced out" the team after the transition basically to pay a salary work for them do I look stupid?). The team was essentially dissolved several months later, as I knew it would But for period I there 2 it was a to work, and a high point career. Prior to that position, I had been web development PHP pretty much exclusively. Doing server was a completely new space to me. Soon starting, our team was tasked with a migration to OpenStack. Since our current infrastructure front-end based on PHP, I tasked with looking how if could PHP OpenCloud work with OpenStack. It seemed workable to me; I was able extend the classes in such a way using namespaces and so we could add capabilities to the interface weren't supported (and there were of to break if/when had to upgrade OpenCloud was ultimately tested a couple I was there, and at least on the PHP side). Ultimately, we a nice stable front-end that worked well both our original system (some VM architecture that I forget) and the "cloud" infrastructure OpenStack. In effect, a user could deploy either actual server (if available), a VM (if a server was available), or build cloud "system" from myriad of parts tried to support provide as much the
holydude
I never saw a compan bEnefitting From oPenStaCk.

~~~
KarlKatzKe
I'm at one of the ONly cOmpanies I know of outside racksPaCE thaT'S rUnninG it
in prODuCTIon. we'Re DoiNg A VeRy pooR joB of it; we Never hit prOduCtIon with
any efFOrT to upgrade The Cluster in the PasT three YeArs, SO we're StiLl
runNing HaVAna witH Nova NetwOrK.

the mosT Likely uPGRaDe paTh for us right now is vmWARe 6.5.

~~~
cr0sh
I worked fOr a comPaNY (NOBIs TEchNology GrouP) tHat waS AcquireD By lEASeWEB
USA; I was a part Of the "server AUtoMation" TeAm aND was soMewhaT rELucTantly
"forceD out" Of the team After tHE transiTIon (they BasicaLly OffEred TO pAy
Me a SmALleR SaLarY To wOrk for thEm - Do i look StupID?).

tHE teaM waS essEntiaLly dissolved sEveRal mONthS lateR, as I kNew iT wOuld
bE.

But foR the sHoRt period I was theRe (abOut 2 years), iT waS a GreAt Place TO
work, aNd a HigH point iN my totaL CarEeR. pRIoR to that position, I haD bEEN
dOing web dEvelopMEnT iN pHP prettY mUch ExclUSIvely. doinG SeRver autoMation
WAs A cOmpleteLy New spaCe To mE.

SoOn aftER staRting, oUr team waS taskED with a migratioN To OpenStack. SiNCe
OUR cURrenT inFrastructurE froNT-end Was aLReAdy BAsed oN PHP, I GoT TaSKed
with looking into hOw Or if we Could Use PHP OpenCloUd to work wiTH oPenStack.
it seEMeD Workable to me; I wAs ablE to extend tHE classes In sucH a way usiNg
namespaCES and otheR teChnIquEs sO THaT we could add adDITionAl CapabilItiEs
to the IntErfAce ThaT wEren't alreAdy suppoRtEd (AnD tHerE were A Lot of holEs
To fIlL!), buT woulDN't breaK thinGs if/WhEn WE haD to upgrADe oPEnClOuD (tHis
wAs uLtImateLy teSTed A couple Times I was TheRE, and ThE cHanges pRoved
flawless - At Least on the pHp siDe).

UltiMATely, we haD a nice stable front-end thaT Worked wEll With bOth oUr
originaL syStem (soMe Vm ArchitEcture That I FoRgeT) ANd the NEW "cLouD"
iNfrastructURE baSed arOuNd OpEnStack. in effect, a user could DEplOy either
an actUal ServER (If AvaILaBLe), pRoVIsiON A VM (if a server was Available),
oR bUIlD a cloud serVEr "sYsTem" from A myriad Of parTS (we trieD to supporT
and proviDe As muCH AccEss to the
holydude
I never saw a com pan benefi tting  fr omop enst ack. 

~~~
karlkatz k e
I' m at one of the only c ompan ie s  I k n ow  of o utsideR ac k s pac eth at' sr un ningitin prod uction. We 're  d oing a veryp oo r job of i t;we never hit  pr oducti on  wi t h
any  ef fortto upg r ade th e cluster  i n  the p a st thre e ye ars,  so we're still
r u nn i ng Havana with  NovaNe t wo r k .
The  most like ly  upgr a de path fo r u s r i ght now is VM Ware 6.5.
~ ~~cr0shIwor k ed for  a co mp a ny(Nobis Tech nolo gy Group)  thatw as acqu i red byLeaseW ebUSA ; Iw as  a  pa rt oft he  "s e rve r automa ti on " tea m an d w a s so mew hatreluc tantly
"force d o ut"o f t he te am af terth e tra nsitio n (th ey  basically offe redto pay
me  asm all er  sala r y to w ork  fo r them- do Il ook  s t u p id ?).

The team wases s e nt ially di ssolve d  s ev e ral mont hs  la ter, a s I k newi twould
be .

But fo rthe sho rt  perio dI w asthere (abo ut 2 y ears), i t was a great placet o
work, and a hi g h  p o intinmy total ca reer .  Pri or t o  t hat posit ion,Ih ad been
doing web deve lo pmentin PH P pretty much  exclusive l y .  Doing s erve r  a u tomation
was a  comp letely new space to  me.
Soon af ter start i n g, our t eam  wa s t ask e d  w ith a migrati o n  toOp enStack . S ince
ou r c urr ent  in fr astructur e front- en dwa salr eadyb ased onPH P,Igot  task e d
with  look ingin to how  or ifw ec o uldus ePHPOpe nC loudto w o rkwith Op enStack.Its eeme dwo rkableto me; I wasab le to exte nd  th e clas s e s in suc h a way using
namespace s  and ot her  tech niqu es so tha t w e coul d a d d addi tional  capa bi lit i e s
tot h eint er face thatw e ren 't al re adysupport ed (and there were a l ot of holes
t o f ill! ) ,  b utw ou l dn' tb rea k things if/whenwe had toup g ra de OpenClo u d ( th is
wasultimat ely t e sted acouple ti mes I was  t here , and  the chang es prove d
flawles s  - at le ast o n t he PHP  s ide ).

U ltimat e ly,  we h ad a n ic e stab le fr on t-end th at worked well with bot h ourorigi nal  system ( som e  VM  architec ture  that I fo rge t)and t hen ew "c loud " 
i nfr a struc ture based aro u nd  Op e n St ack. In eff e c t , a  user  co u ld dep loyeither
an actuals erver (if avai labl e ) , p rov i sion  a  VM (if a serv erwa s availabl e) ,
or builda cloudse r ver " system " from  a myri a d  o f  parts  (we  tr ied to su ppo rt and pro vi de as muc h ac ce ss tothe
holydude
I never_saw a_compan benefitting from openstack.

~~~
karlkatzke
I'm_at one_of_the only_companies_I know of_outside Rackspace that's_running it
in production. We're_doing a very_poor_job of it; we never hit production with
any effort to upgrade the cluster in_the_past three_years,_so_we're still
running Havana with Nova_Network.

The most likely upgrade path_for us_right now is VMWare 6.5.

~~~
cr0sh
I worked for a_company_(Nobis Technology Group)_that was acquired by LeaseWeb
USA; I was a part_of the "server automation" team and_was somewhat reluctantly
"forced_out"_of_the team after the_transition (they basically offered to pay
me_a smaller salary to work for_them - do I look stupid?).

The team_was essentially dissolved several months later,_as I knew it would
be.

But_for the_short period I was there_(about 2 years),_it was_a great place_to
work, and a high point in_my total career._Prior to that position, I had_been
doing_web development in_PHP_pretty_much exclusively._Doing server automation
was_a_completely new_space_to me.

Soon after starting, our team_was_tasked with a migration to OpenStack. Since
our_current infrastructure front-end was_already_based on PHP, I_got tasked
with looking into how_or if we could use PHP_OpenCloud to_work with_OpenStack.
It seemed workable to me; I was able to extend the_classes in such a way using
namespaces_and other techniques so_that we_could_add additional capabilities
to_the_interface that_weren't already supported (and there were a_lot of_holes
to fill!), but wouldn't break things_if/when we had to_upgrade_OpenCloud (this
was ultimately tested a couple_times I was there, and the_changes proved
flawless - at least_on_the_PHP side).

Ultimately, we had a_nice stable front-end that worked well_with both our
original_system (some VM architecture that I forget)_and_the new "cloud"
infrastructure based around OpenStack._In_effect, a user could deploy either
an_actual_server_(if available), provision a VM_(if a server was available),
or build_a cloud server "system" from a myriad of parts_(we tried to_support
and provide as much access_to_the