The tests shouldn't overlap the AWS certs but it's such a gorilla that many people have to be aware of some fundamentals. E.g., there's a good chance that the systems you're configuring and maintaining are on EC2 instances. You can treat this as simple PAAS provisioning but since the 201 covers capacity planning I think that knowing that AWS and other cloud providers can be used for elasticity - to "scale out" instead of "scale up" - is worth at least a point. That could mean a greater emphasis on integrating other services than the less common configuration options.
For instance let's take a postfix server. The cloud monitor could launch a new instance when the existing servers reach 80% capacity for more than an hour. You can take your time ahead of time testing the server configuration with manual in hand so you don't have to memorize the details of obscure features. You just need to know that they're there. My big needs are how do you automate integration into the system? E.g., how do you configure the server to use LDAP for user details? Can you require strong mutual authentication using digital certs? Kerberos? How do you specify where the mail is written and will there be problems if multiple email servers are writing to it? For what it's worth we've had the production team maintain our dev/qa servers but we have so many different combinations that we're paying a fortune for servers that are rarely used. As a devop I've been tasked with finding a solution that meets the needs of the dev and qa teams and not just take on the responsibilities previously done by the production team. My proposal is a webapp (HTML, REST) where a person or test script can ask for a 4 hour lease on, oh, a MySQL database with certain properties. It will be entirely automated - a lot like automatic provisioning by a cloud provider. (In fact we may end up using that on our back end.) I need to know how to set up different configurations but more importantly I need to know how to integrate these systems into our existing infrastructure. The current approach has been very ad hoc but that only worked since the systems stayed up. With ephemeral instances we need standardization. Knowing details, e.g., that ChallengeResponse + PAM means that a server may accept passwords even though PasswordAuthentication is off is also important but it's secondary (at the moment) to being able to automate everything. I know this is very different from the classic ops needs that the current exams test. I just wanted to toss out a similar set of job requirements, one with a lot of overlap but some key differences. Bear On Mon, Nov 19, 2018 at 12:20 PM Bryan Smith <[email protected]> wrote: > Ceph RADOSGW provides a S3 compatible API ... and is Open Source. > AWS is not. > > If anything is added to the 200 level > > - bjs > > P.S. This is why I'm in favor of splitting HA (and LB) concepts from > Storage, at the 300 level. > > P.P.S. Sorry I haven't been around. Been slammed by work and other > things well into the evening and weekends, continually. That and 30 years > as an UCF grad and alumni on Saturday. ;) > > > On Mon, Nov 19, 2018 at 12:12 PM Simone Piccardi <[email protected]> > wrote: > >> Il 19/11/18 17:10, Bear Giles ha scritto: >> > How could I forget using S3 as a web server for static content? (With >> > client-side javascript libraries and lambdas that means you can often >> > create "serverless" websites.) Candidates shouldn't need to know the >> > details but should know that S3 is an alternative to apache and nginx, >> > and they should know that you can configure S3 so it sends an alert >> when >> > a file is deleted and that means you can use cheaper 'spot instances' >> > for scalability using cheaper spot instances. For instance you may have >> > full-resolution video on permanent S3 and video in different formats on >> > spot storage. When the latter file is deleted it automatically triggers >> > a process that will recreate it. This is usually finished by the time a >> > user requests a copy of the file, esp. if you are also using a caching >> > layer. >> > >> > Candidates shouldn't need to know the details of how to do this but >> they >> > should understand that a request for a "web server" might be satisfied >> > by S3 and a lighter EC2 instance instead of a more expensive EBS and a >> > heftier EC2 instance running the web server that provides the same >> > static content. Or that if devs use S3 storage they may also may also >> > need SNS (iirc) so they can receive notifications. SNS means knowing >> > that the could be linked to other messaging tools, e.g., SQS that acts >> > as a JMS server. >> > >> > It sounds like I'm arguing for a cloud-specific LPIC-2 but people still >> > need to be able to set up most (not all) conventional servers as well. >> > That's especially true with privacy laws that have a consequence of >> > encouraging hybrid solutions where sensitive information is stored in a >> > small data center the company controls while the public access is >> > entirely done in a scalable public cloud. No unencrypted sensitive >> > information would ever be on the public cloud, not even only in memory. >> > Someone in that situation needs to know the costs and benefits of both >> > S3 and apache/nginx, of RDS and their own oracle/mssql/mysql/postgresql >> > server, etc. >> >> I was thinking that 202 is a Linux senior sysadmin exam, it seems to me >> that you are talking about an Amazon services admin exams. >> >> Don't see anything on this regarding Linux knowledge. But probably I'm >> missing something. >> >> >> Regards >> Simone >> -- >> Simone Piccardi Truelite Srl >> [email protected] (email/jabber) Via Monferrato, 6 >> Tel. +39-347-1032433 50142 Firenze >> http://www.truelite.it Tel. +39-055-7879597 >> _______________________________________________ >> lpi-examdev mailing list >> [email protected] >> http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev >> > > > -- > > -- > Bryan J Smith - http://www.linkedin.com/in/bjsmith > E-mail: b.j.smith at ieee.org or me at bjsmith.me > _______________________________________________ > lpi-examdev mailing list > [email protected] > http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
_______________________________________________ lpi-examdev mailing list [email protected] http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
