Infrastructure Technologist at a tech consulting company with 1-10 employees
Real User
2020-03-23T06:14:00Z
Mar 23, 2020
My advice to someone considering this solution is to take a pragmatic approach, there are set pieces in a hybrid cloud deployment and you have to do a proof of concept with. You have to go in and do an audit. You've got to create a statement of work. You've got to identify, who are the administrators or who's impacted by any downtime once you try to introduce this. You've got to be able to sandbox it. Duplicate the environment in a lab and then sandbox the improvements that you want to integrate and then you got to roll out a pilot and try it. My biggest pet peeve about doing anything with clouds is that once you sign up for something on the cloud, you don't have any control over what they do with that information. Because of the convenience, nobody thinks about the consequence of putting that stuff out there and what they're going to do with it. Unless you're super technical, you have no concept of what's being done. All you know is that you are getting what you want and you really don't want to burden yourself with figuring out on what's being done. If you knew what's being done, you wouldn't do it. What people don't know, is that IPV6 is the back door. This is where the security issue comes in. IPV6 is the back door for Microsoft all of the network operating. You have to go in and turn it off manually. You have to understand those things too. It's second nature for people who work on the environment, but we have to be aware of that because when you're troubleshooting in a hybrid environment, you have to rely on whether it's the existing documentation; you have to rely on your working knowledge about how things connect and what have you, and then you have to try and figure out what's been done. You also have to identify what's on and what's not on; and who's talking and where. So the hybrid cloud adds a layer of complexity as opposed to having two separate environments to log into; the on-premise environment in the cloud environment. If you're separate, it makes it a lot easier. But when you're integrated, you're bringing in a whole can of worms at that point. The next feature I would like to have full disclosure of what's being done with the data. I would rate it a ten out of ten. But it's a catch 22. It requires a thorough understanding of what the limitations are and what the consequences of utilizing the system itself or trying to accept those limitations.
CloudSphere is an intelligent cloud management platform that enables organizations to plan, optimize, secure, and scale their cloud adoption. The platform has three solutions to help organizations manage dynamic, multi-cloud environments, including cloud migration planning, cloud cost management, and cloud security posture management. By using application intelligence (AI), the platform is able to discover and collect all of the data points that collectively define an application across...
My advice to someone considering this solution is to take a pragmatic approach, there are set pieces in a hybrid cloud deployment and you have to do a proof of concept with. You have to go in and do an audit. You've got to create a statement of work. You've got to identify, who are the administrators or who's impacted by any downtime once you try to introduce this. You've got to be able to sandbox it. Duplicate the environment in a lab and then sandbox the improvements that you want to integrate and then you got to roll out a pilot and try it. My biggest pet peeve about doing anything with clouds is that once you sign up for something on the cloud, you don't have any control over what they do with that information. Because of the convenience, nobody thinks about the consequence of putting that stuff out there and what they're going to do with it. Unless you're super technical, you have no concept of what's being done. All you know is that you are getting what you want and you really don't want to burden yourself with figuring out on what's being done. If you knew what's being done, you wouldn't do it. What people don't know, is that IPV6 is the back door. This is where the security issue comes in. IPV6 is the back door for Microsoft all of the network operating. You have to go in and turn it off manually. You have to understand those things too. It's second nature for people who work on the environment, but we have to be aware of that because when you're troubleshooting in a hybrid environment, you have to rely on whether it's the existing documentation; you have to rely on your working knowledge about how things connect and what have you, and then you have to try and figure out what's been done. You also have to identify what's on and what's not on; and who's talking and where. So the hybrid cloud adds a layer of complexity as opposed to having two separate environments to log into; the on-premise environment in the cloud environment. If you're separate, it makes it a lot easier. But when you're integrated, you're bringing in a whole can of worms at that point. The next feature I would like to have full disclosure of what's being done with the data. I would rate it a ten out of ten. But it's a catch 22. It requires a thorough understanding of what the limitations are and what the consequences of utilizing the system itself or trying to accept those limitations.