Cp rackspace control panel admin12/16/2023 ![]() ![]() Neither interpretation is necessarily right, but in this era it's definitely time to rethink what customer needs are (if you're outlining a migration path). My point is that you might be measuring customer needs/migration path in a way differently than customers do (if you repeatedly see them move away to a 3rd party, especially one particular 3rd party).Ī common theme in this thread is that people inside Rackspace see Rackspace Cloud + Slicehost as very similar, because 1) they have a common corp ownership 2) they have an increasingly common (but hidden-to-users) back-end 3) they have common staff in some cases.īut the customers in this thread see Linode + Slicehost as much more similar because 1) their control panels are a bit more similar 2) they share DNS flexibility + other featuers 3) Price (Linode moving in more attractive direction for some use-cases). Trust me that these guys are really working for the best for you all. There are some serious champions of Slicehost at Rackspace both in the form of former Slicehost employees still there (Paul Tomes, article site creator) and long time Rackers. I definitely can see this from all sides and for Slicehost customers, all I can say is that at no point along the way did anyone (at Slicehost or Rackspace) ever have less than the best intentions for the brand and the community. What matters is having your interests be in the direct path for the company that is serving you and as a Rackspace Cloud customer you'll have that, while as a Slicehost customer you did not (post acquisition). I honestly think everyone would have been better off if we just ripped the band-aid early and tried to figure out how to make the core Cloud Server community out of the incoming Slicehost customers.Ĭontrol panels, features, pricing, etc all change and in the long run are only ephemerally important. Unfortunately I think in hindsight I can say that our decision was probably the wrong call. We succeeded in that goal but the net effect (unintentionally so) was to disconnect Slicehost from Rackspace's cloud roadmap and effectively strand the product. It was honestly a very very tough call and at the time the thing we all (Matt, me and Rackspace) were most sensitive to was to not disrupt the Slicehost community. ![]() Given that this is a public plan now I feel like I can share that during the acquisition process of Slicehost we debated heavily what the right thing was to do with the brand. I founded Slicehost (with Matt Tanase) and I absolutely think this is the right thing to do and definitely is the best thing for existing Slicehost customers. Definitely a misleading title and kind of unfair to Rackspace. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |