01. Adrian Otto, Rackspace, Visits theCUBE . (00:20)
02. Rackspace CoFounded OpenStack. (00:53)
03. Offering Support on OpenStack Clouds and Azure. (01:37)
04. Partnership with Intel. (03:00)
05. How Rackspace Supports Azure. (04:35)
06. Managing the Customer's Perspective and Needs. (05:35)
07. The Cloud-First Policy. (07:08)
08. Impact of the Containerization Movement. (08:16)
#theCUBE #RackSpace #OSSV #OpenStackSV #OpenStack #OSSV15 #SiliconANGLE
--- ---
Containers are now a ‘movement’ | #OSSV15
by Betsy Amy-Vogt | Aug 26, 2015
“Rackspace is defined by service to our customers,” said Adrian Otto, distinguished architect at Rackspace, Inc., defending the company’s decision to support MS Azure. “In the Microsoft space, customers love Azure.”
As one of the cofounders and long-time leaders in the OpenStack Foundation, Rackspace wants to extend its vision to allow customers to experience Rackspace’s support experience on whatever infrastructure they choose. The choice depends on the customer’s needs.
Speaking with Jeff Frick cohost of @theCUBE, during OpenStack Silicon Valley 2015, Otto discussed the collaboration between Rackspace and Intel Corp. He said that it is “more than developers working together. It is the largest test cluster ever put together for OpenStack” and that they are both committed to OpenStack as an innovation driver.
Describing Rackspace’s Magnum project as “Containers as a Service experience for customers,” Otto said that customers can trust Magnum to be a multi-tenant solution that allows isolation: “Magnum is a way to orchestrate your container system in a way that is safe.”
Imperative vs. declarative
Otto defined the difference between imperative and declarative systems, as well as how each different system appeals to different customer needs. A declarative system requires specifying just the result, and therefore the instruction set is simple. An example of this is Kubernetes, an open-source orchestration system for Docker containers. Imperative is the opposite and requires a more complex instruction set, which may be more appropriate for some customer needs. An example is Docker Swarm, native clustering for Docker.
@theCUBE
#OpenStackSV
Forgot Password
Almost there!
We just sent you a verification email. Please verify your account to gain access to
OpenStack Silicon Valley 2015 | Mountain View. If you don’t think you received an email check your
spam folder.
Sign in to OpenStack Silicon Valley 2015 | Mountain View.
In order to sign in, enter the email address you used to registered for the event. Once completed, you will receive an email with a verification link. Open this link to automatically sign into the site.
Register For OpenStack Silicon Valley 2015 | Mountain View
Please fill out the information below. You will recieve an email with a verification link confirming your registration. Click the link to automatically sign into the site.
You’re almost there!
We just sent you a verification email. Please click the verification button in the email. Once your email address is verified, you will have full access to all event content for OpenStack Silicon Valley 2015 | Mountain View.
I want my badge and interests to be visible to all attendees.
Checking this box will display your presense on the attendees list, view your profile and allow other attendees to contact you via 1-1 chat. Read the Privacy Policy. At any time, you can choose to disable this preference.
Select your Interests!
add
Upload your photo
Uploading..
OR
Connect via Twitter
Connect via Linkedin
EDIT PASSWORD
Share
Forgot Password
Almost there!
We just sent you a verification email. Please verify your account to gain access to
OpenStack Silicon Valley 2015 | Mountain View. If you don’t think you received an email check your
spam folder.
Sign in to OpenStack Silicon Valley 2015 | Mountain View.
In order to sign in, enter the email address you used to registered for the event. Once completed, you will receive an email with a verification link. Open this link to automatically sign into the site.
Sign in to gain access to OpenStack Silicon Valley 2015 | Mountain View
Please sign in with LinkedIn to continue to OpenStack Silicon Valley 2015 | Mountain View. Signing in with LinkedIn ensures a professional environment.
Are you sure you want to remove access rights for this user?
Details
Manage Access
email address
Community Invitation
Adrian Otto, Rackspace | Open Stack Silicon Valley 2015
01. Adrian Otto, Rackspace, Visits theCUBE . (00:20)
02. Rackspace CoFounded OpenStack. (00:53)
03. Offering Support on OpenStack Clouds and Azure. (01:37)
04. Partnership with Intel. (03:00)
05. How Rackspace Supports Azure. (04:35)
06. Managing the Customer's Perspective and Needs. (05:35)
07. The Cloud-First Policy. (07:08)
08. Impact of the Containerization Movement. (08:16)
#theCUBE #RackSpace #OSSV #OpenStackSV #OpenStack #OSSV15 #SiliconANGLE
--- ---
Containers are now a ‘movement’ | #OSSV15
by Betsy Amy-Vogt | Aug 26, 2015
“Rackspace is defined by service to our customers,” said Adrian Otto, distinguished architect at Rackspace, Inc., defending the company’s decision to support MS Azure. “In the Microsoft space, customers love Azure.”
As one of the cofounders and long-time leaders in the OpenStack Foundation, Rackspace wants to extend its vision to allow customers to experience Rackspace’s support experience on whatever infrastructure they choose. The choice depends on the customer’s needs.
Speaking with Jeff Frick cohost of @theCUBE, during OpenStack Silicon Valley 2015, Otto discussed the collaboration between Rackspace and Intel Corp. He said that it is “more than developers working together. It is the largest test cluster ever put together for OpenStack” and that they are both committed to OpenStack as an innovation driver.
Describing Rackspace’s Magnum project as “Containers as a Service experience for customers,” Otto said that customers can trust Magnum to be a multi-tenant solution that allows isolation: “Magnum is a way to orchestrate your container system in a way that is safe.”
Imperative vs. declarative
Otto defined the difference between imperative and declarative systems, as well as how each different system appeals to different customer needs. A declarative system requires specifying just the result, and therefore the instruction set is simple. An example of this is Kubernetes, an open-source orchestration system for Docker containers. Imperative is the opposite and requires a more complex instruction set, which may be more appropriate for some customer needs. An example is Docker Swarm, native clustering for Docker.
@theCUBE
#OpenStackSV
