5fca287eb5
There are several instances of "Block Storage Service" in the upstream documentation. As was recently clarified in the docs mailing list, these should be "Block Storage service". This patch applies the fix. Change-Id: I591c100ab031b75f1c0d27d45f53e32401a26e30 Partial-Bug: #1217503
385 lines
17 KiB
XML
385 lines
17 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
|
|
xml:id="associate-controller-node-quiz">
|
|
<?dbhtml stop-chunking?>
|
|
<title>Controller Node Quiz</title>
|
|
<section xml:id="associate-day-one-controller-quiz-schedule">
|
|
<title>Day 1, 14:25 to 14:45</title>
|
|
<formalpara>
|
|
<title>Associate Training Guide, Controller Node Quiz Questions</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>When managing images for OpenStack you can complete all those tasks with the OpenStack
|
|
dashboard. (True or False)</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>True</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>False</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>When setting up access and security, SSH credentials (keypairs) must be injected
|
|
into images after they are launched with a script. (True or False)</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>True</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>False</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>You can track monthly costs with metrics like: (choose all that apply)</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>VCPU</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>QoS</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Uptime</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Disks</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>RAM</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>The following OpenStack command-line clients are available. (choose all that apply)</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>python-keystoneclient</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>python-hypervisorclient</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>python-imageclient</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>python-cinderclient</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>python-novaclient</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>To install a client package</title>
|
|
<para>
|
|
Run this command:
|
|
<screen><prompt>#</prompt> <userinput>pip install [--update] python-project client (True or False)</userinput></screen>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>True</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>False</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>To list images</title>
|
|
<para>
|
|
Run this command:
|
|
<screen><prompt>$</prompt> <userinput>glance image-list</userinput></screen>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>True</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>False</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>When troubleshooting image creation you will need to look at which of the following
|
|
log files for errors? (choose all that apply)</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>Examine the /var/log/nova-api.log</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Examine the /var/log/nova-compute.log</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Examine the /var/log/nova-error.log</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Examine the /var/log/nova-status.log</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Examine the /var/log/nova-image.log</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>To generate a keypair use the following command syntax:
|
|
$ nova keypair-add --pub_key ~/.ssh/id_rsa.pub KEY_NAME</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>True</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>False</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>When you want to launch an instance you can only do that from an image. (True or False)</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>True</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>False</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>An instance has a Private IP address which has the following properties? (choose all that apply)</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>Used for communication between instances</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>VMware vShpere 4.1, update 1 or greater</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Stays the same, even after reboots</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Stays allocated, even if you terminate the instance</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>To see the status of the Private IP addresses you use the following command:
|
|
$ nova floating-ip-pool-list</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>To start and stop and instance you can use the following options: (choose all that apply)</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>Pause/Un-pause</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Suspend/Resume</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Reboot</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Evacuate</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Shutdown/Restart</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>To create a network in OpenStack use the following command: $ neutron net-create net1 (True or False)</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>True</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>False</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>Identity Service provides the following functions: (choose all that apply)</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>Group policy objects</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Message queuing</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>User management</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Publishing</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Service catalog</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>The AMQP supports the following messaging bus options: (choose all that apply)</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>ZeroMQ</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>RabbitMQ</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Tibco Rendezvous</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>IBM WebSphere Message Broker</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>Qpid</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
<listitem>
|
|
<formalpara>
|
|
<title>OpenStack uses the term tenant but in earlier versions it used the term customer. (True or False)</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>True</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>False</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
<formalpara>
|
|
<title>Associate Training Guide, Controller Node Quiz Answers</title>
|
|
<para>
|
|
<orderedlist>
|
|
<listitem>
|
|
<para>B (False) - you can manage images through only the glance and nova clients or the Image
|
|
Service and Compute APIs.</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>B (False) - Keypairs are SSH credentials that are injected into images when they are launched.
|
|
For this to work, the image must contain the cloud-init package</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>A, C, D, E - You can track costs per month by showing metrics like number of VCPUs, disks,
|
|
RAM, and uptime of all your instances</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>A, D, E - The following command-line clients are available for the respective services' APIs:
|
|
cinder(python-cinderclient)
|
|
Client for the Block Storage service API. Use to create and manage volumes.
|
|
glance(python-glanceclient)
|
|
Client for the Image Service API. Use to create and manage images.
|
|
keystone(python-keystoneclient)
|
|
Client for the Identity Service API. Use to create and manage users, tenants, roles, endpoints, and credentials.
|
|
nova(python-novaclient)
|
|
Client for the Compute API and its extensions. Use to create and manage images, instances, and flavors.
|
|
neutron(python-neutronclient)
|
|
Client for the Networking API. Use to configure networks for guest servers. This client was previously known as neutron.
|
|
swift(python-swiftclient)
|
|
Client for the Object Storage API. Use to gather statistics, list items, update metadata, upload, download and delete files stored by the object storage service. Provides access to a swift installation for ad hoc processing.
|
|
heat(python-heatclient)</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>A (True)</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>A (True)</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>A, B</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>B (False) - $ nova keypair-add KEY_NAME > MY_KEY.pem</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>B (False) - you can launch and instance from an image or a volume</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>A, B, C</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>A, B, C, D</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>A (True)</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>C, E</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>A, B, E</para>
|
|
</listitem>
|
|
<listitem>
|
|
<para>B (False) - Because the term project was used instead of tenant in earlier versions of
|
|
OpenStack Compute, some command-line tools use --project_id instead of --tenant-id or
|
|
--os-tenant-id to refer to a tenant ID.</para>
|
|
</listitem>
|
|
</orderedlist>
|
|
</para>
|
|
</formalpara>
|
|
</section>
|
|
</chapter>
|