On Fri, Jun 21, 2013 at 12:23 PM, <[email protected]> wrote: > ** > > Big IT shops (at least the ones I know here in Brazil) tend to have a > storage crew, a security/identity crew, a virtualization/OS crew... and > nothing prevents anyone from getting multiple specialties. > Actually, the cloud and software-based storage is changing this.
For example, even if I'll actually configure my cloud to use a identity > management solution, I do not need to know how to deploy and tune the > identity solution itself. I'd need some ldap, ssl and kerberos concepts, > Actually, a lot of IdM specialists aren't very familiar with these concepts -- e.g., MCITP/MCSA/MCSE. ;) Same for storage: I don't need to be a EMC FibreChannel storage manager, > neither an openfiler manager, a gluster admin or even know how to setup > pacemaker for HA to be able to deploy a nice opencloud in premises. > Ummm ... I think you're missing concurrent, distributed storage access concepts -- especially for writes, with locking, etc... -- with others. In fact, if there is a gross deficiency in the Linux world, it is here. I.e., taking stateless HA/LB concepts for web services and applying them to concurrent, distributed storage access concepts. Doesn't matter if it's hardware or software-based, locking, coherency and other things are not optional concepts to learn on the platform (e.g., Linux) when more than one host or instance can write to the storage. But I'd need to know what is a iSCSI initiator, demand multipath for > resiliency, choose raid levels or choose an object store so my cloud > instances can connect to their storage appliances or services. All > client-side stuff, and some concepts for planning. > Actually, software-based storage removes much of this. And in the age of Big Data and Cloud, it scales much better. That's why Ceph and Gluster (Red Hat Storage) are popular, as well as more Cloud interfaces like Hadoop and Swift (which can be backed and serviced by Ceph and/or Gluster, etc...). > If I deploy a small private cloud for a medium enterprise, probably any > entry-level NFS NAS would be enough, or I'd use the cloud own object store > services for storage, leveraging the cloud servers internal disks. > But _how_ do you do that? I.e., I think you're ignoring a big piece there. ;) > I would not need profound storage and security knowledge, even if the > could setup per se would be a Level 3 specialty. In the future I even think > cloud and virtualization would stop being distinct specialties, but not now > (for the current LPI revisions). > Again, LPI is not the only organization dealing with this. ;) E.g., Red Hat has introduced a whole new series of 2xx-level classes that are typically 2-days, and try to cover most of the components in many, emerging technologies. There is one on OpenStack, another on Storage (Gluster), etc... But tying in RHEV with OpenStack, OpenStack with Storage, RHEV with Storage, etc... is a bit more complicated. Even though RHEV doesn't need OpenStack, can use other Storage than Storage (Gluster), and OpenStack has other options than RHEV or Storage (Gluster), etc... Again, LPI is not the only organization dealing with this. And not just for training, but for partners and channel too. -- bjs P.S. The partner/channel is literally "my day job" -- most specifically, I'm "the" Storage (Gluster) and one of the OpenStack (RDO) SMEs. ;) -- Bryan J Smith - Professional, Technical Annoyance b.j.smith at ieee.org - http://www.linkedin.com/in/bjsmith
_______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
