1. Log in to the dashboard and choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the Identity Panel tab and select the Projects category.

3. Click Create Project.

4. On the Project Info tab in the Create Project window, enter a name and description for the project. By default, the project is enabled. See Section 2.1, “Consequences of disabling projects and users”.

5. On the Project Members tab, add members to the project.

6. On the Quota tab, edit quota values.

7. Click Create Project.

   The Projects category shows the project, including its assigned ID.

1. On the Admin tab, click the Identity Panel tab and select the Projects category.

2. Select the project that you want to update.

3. In the More drop-down list, click Edit Project.

4. In the Edit Project window, you can update a project to change its name or description, and enable or temporarily disable it.

   By default, the project is enabled. To temporarily disable it, clear the Enabled check box. To enable a disabled project, select the Enabled check box.

5. Click Save.

1. On the Admin tab, click the Identity Panel tab and select the Projects category.

2. Select a project to modify its user assignments.

3. Click the selected project's Modify Users button.

   The Edit Project window shows the following lists of users:

   • All Users. Users that are available to be assigned to the current project.

   • Project Members. Users that are assigned to the current project,

   Figure 2.3. Edit the users list

   

4. To assign a user to the current project, click + for the user.

   The user moves from the All Users list to the Project Members list.

5. To remove a user from the current project, click the - button for the user.

   The user moves from the Project Members list to the All Users list.

6. Click Save.

1. On the Admin tab, click the Identity Panel tab and select the Projects category.

2. Select the projects that you want to delete.

3. Click Delete Projects to confirm the deletion.

   Note

   You cannot undo the delete action.

1. Log in to the dashboard and choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the Identity Panel tab and select the Users category.

3. Click Create User.

4. In the Create User window, enter a user name, email, and preliminary password for the user. Confirm the password.

   Select a project from the Primary Project drop-down list.

   Choose a role for the user from the Role drop-down list. Default is _member_.

5. Click Create User to confirm your changes.

   Respond to the prompt to remember the password for the user.

   The dashboard assigns an ID to the user, and the user appears in the Users category.

1. On the Admin tab, click the Identity Panel tab and select the Users category.

2. Select the user that you want to disable or enable. You can disable or enable only one user at a time.

3. In the Actions drop-down list, select Disable User or Enable User.

   In the Enabled column, the enabled value updates to either True or False.

1. On the Admin tab, click the Identity Panel tab and select the Users category.

2. Select the users that you want to delete.

3. Click Delete Users.

4. In the Confirm Delete Users window, click Delete Users to confirm the deletion.

1. Log in to the dashboard and choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the Instances category.

3. Select an instance to create a snapshot from it. From the Actions drop-down list, select Create Snapshot.

4. In the Create Snapshot window, enter a name for the snapshot. Click Create Snapshot. The dashboard shows the instance snapshot in the Images & Snapshots category.

5. To launch an instance from the snapshot, select the snapshot and click Launch.

1. Log in to the dashboard and choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the Instances category.

3. Select the instance for which you want to change the state.

4. In the More drop-down list in the Actions column, select the state.

   Depending on the current state of the instance, you can choose to pause, un-pause, suspend, resume, soft or hard reboot, or terminate an instance (items in red are disabled).

   Figure 2.4. Dashboard-Instance Actions

   

1. Log in to the dashboard and choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the Instances category.

3. Select a month and click Submit to query the instance usage for that month.

4. Click Download CSV Summary to download a CSV summary.

1. Log in to the dashboard and choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the Volumes category.

3. Click Create Volume Type.

   In the Create Volume Type window, enter a name for the volume type.

4. Click Create Volume Type to confirm your changes.

1. Log in to the dashboard and choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the Volumes category.

3. Select the volume type or types that you want to delete.

4. Click Delete Volume Types.

5. In the Confirm Delete Volume Types window, click Delete Volume Types to confirm the action.

6. A message indicates whether the action succeeded.

1. Log in to the dashboard and choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the Volumes category.

3. Select the volume or volumes that you want to delete.

4. Click Delete Volumes.

5. In the Confirm Delete Volumes window, click Delete Volumes to confirm the action.

6. A message indicates whether the action succeeded.

1. Log in to the dashboard.

   Choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the Images category. The images that you can administer for cloud users appear on this page.

3. Click Create Image.

4. In the Create An Image window, enter or select the following values:

   Name	Enter a name for the image.
   Description	Enter a brief description about the image.
   Image Source	Choose the image source from the dropdown list. Your choices are Image Location and Image File.
   Image File or Image Location	Based on your selection, there is an Image File or Image Location field. You can include the location URL or browse for the image file on your file system and add it.
   Format	Select the image format.
   Minimum Disk (GB) and Minimum RAM (MB)	Leave these fields empty.
   Public	Select this option to make the image public to all users.
   Protected	Select this option to ensure that only users with permissions can delete the image.

5. Click Create Image.

   The image is queued to be uploaded. It might take some time before the status changes from queued to active.

1. Log in to the dashboard.

   Choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the Images category.

3. Select the image that you want to edit. Click Edit.

4. In the Update Image window, you can change the name for the image. Select the Public check box to make the image public. Clear this check box to make the image private. You cannot change the kernel ID, RAM disk ID, or architecture attributes for an image.

5. Click Update Image.

1. Log in to the dashboard.

   Choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the Images category.

3. Select the images that you want to delete.

4. Click Delete Images.

5. In the Confirm Delete Image window, click Delete Images to confirm the deletion.

   You cannot undo this action.

1. Log in to the dashboard.

   Choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the Flavors category.

3. Click Create Flavor.

4. In the Create Flavor window, enter or select the following values:

   Flavor Info tab
   Name	Enter the flavor name.
   ID	The flavor ID, generated by OpenStack.
   VCPUs	Enter the number of virtual CPUs to use.
   RAM MB	Enter the amount of RAM to use, in megabytes.
   Root Disk GB	Enter the mount of disk space in gigabytes to use for the root (/) partition.
   Ephemeral Disk GB	Enter the amount of disk space in gigabytes to use for the ephemeral partition. If unspecified, the value is 0 by default. Ephemeral disks offer machine local disk storage linked to the life cycle of a VM instance. When a VM is terminated, all data on the ephemeral disk is lost. Ephemeral disks are not included in any snapshots.
   Swap Disk MB	Enter the amount of swap space (in megabytes) to use. If unspecified, the default is 0.

5. In the Flavor Access tab, you can control access to the flavor by moving projects from the All Projects column to the Selected Projects column.

   Only projects in the Selected Projects column can use the flavor. If there are no projects in the right column, all projects can use the flavor.

6. Click Create Flavor.

1. Log in to the dashboard.

   Choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the Flavors category.

3. To edit a flavor:

   1. Select the flavor that you want to edit. Click Edit Flavor.

   2. In the Edit Flavor window, update the flavor name, VCPUs, RAM, root disk, ephemeral disk, and swap disk values in the Flavor Info tab.

   3. In the Flavor Access tab, use + to control the access by moving projects from the left column to the right column.

      Note

      You can also perform this action by choosing Modify Access from the More dropdown list from the Actions column.

   4. Click Save.

4. To create new extra spec key-value pair:

   1. Select the flavor that you want to edit. Click More.

   2. Choose View Extra Specs from the dropdown list.

   3. Click Create.

   4. Select Keys from the dropdown list.

   5. Enter values for Key and Value.

   6. Click Save.

1. Log in to the dashboard.

   Choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the Flavors category.

3. Select the flavors that you want to delete.

4. Click Delete Flavors.

5. In the Confirm Delete Flavors window, click Delete Flavors to confirm the deletion. You cannot undo this action.

1. Log in to the OpenStack dashboard and choose the admin project from the Current Project Project_Name drop-down list.

   Here Project_Name is the name of the current project.

2. On the Admin tab, click the System Info category.

3. Click the:

   • Services tab to view services information.

     The page displays the internal name and the public OpenStack name for the service, the host where the service runs, and whether the service is or is not enabled.

   • Compute Services tab to view services specific to the Compute Service. Both host and zone are listed for each service, as well as its activation status.

Procedure 3.1. List and view current security groups

From the command line you can get a list of security groups for the project, using the nova command:

1. Ensure your system variables are set for the user and tenant for which you are checking security group rules for. For example:

   ​export OS_USERNAME=demo00
   ​export OS_TENANT_NAME=tenant01

2. Output security groups, as follows:

   $ nova secgroup-list
   +---------+-------------+
   | Name    | Description |
   +---------+-------------+
   | default | default     |
   | open    | all ports   |
   +---------+-------------+

3. View the details of a group, as follows:

   $ nova secgroup-list-rules groupName

   For example:

   $ nova secgroup-list-rules open
   +-------------+-----------+---------+-----------+--------------+
    | IP Protocol | From Port | To Port | IP Range  | Source Group |
    +-------------+-----------+---------+-----------+--------------+
    | icmp        | -1        | 255     | 0.0.0.0/0 |              |
    | tcp         | 1         | 65535   | 0.0.0.0/0 |              |
    | udp         | 1         | 65535   | 0.0.0.0/0 |              |
    +-------------+-----------+---------+-----------+--------------+

   These rules are allow type rules as the default is deny. The first column is the IP protocol (one of icmp, tcp, or udp). The second and third columns specify the affected port range. The third column specifies the IP range in CIDR format. This example shows the full port range for all protocols allowed from all IPs.

Procedure 3.2. Create a security group

When adding a new security group, you should pick a descriptive but brief name. This name shows up in brief descriptions of the instances that use it where the longer description field often does not. For example, seeing that an instance is using security group "http" is much easier to understand than "bobs_group" or "secgrp1".

1. Ensure your system variables are set for the user and tenant for which you are checking security group rules for.

2. Add the new security group, as follows:

   $ nova secgroup-create Group Name Description

   For example:

   $ nova secgroup-create global_http "Allows Web traffic anywhere on the Internet."
   +---------------------+-------------+----------------------------------------------+
   | Id                  | Name        | Description                                  |
   +---------------------+-------------+----------------------------------------------+
   | 1578a08c-...dd9f23b | global_http | Allows Web traffic anywhere on the Internet. |
   +---------------------+-------------+----------------------------------------------+

3. Add a new group rule, as follows:

   $ nova secgroup-add-rule secGroupName ip-protocol from-port to-port CIDR

   The arguments are positional, and the "from-port" and "to-port" arguments specify the local port range connections are allowed to access, not the source and destination ports of the connection. For example:

   $ nova secgroup-add-rule global_http tcp 80 80 0.0.0.0/0
   +-------------+-----------+---------+-----------+--------------+
   | IP Protocol | From Port | To Port | IP Range  | Source Group |
   +-------------+-----------+---------+-----------+--------------+
   | tcp         | 80        | 80      | 0.0.0.0/0 |              |
   +-------------+-----------+---------+-----------+--------------+

   You can create complex rule sets by creating additional rules. For example, if you want to pass both http and https traffic, run:

   $ nova secgroup-add-rule global_http tcp 443 443 0.0.0.0/0
   +-------------+-----------+---------+-----------+--------------+
   | IP Protocol | From Port | To Port | IP Range  | Source Group |
   +-------------+-----------+---------+-----------+--------------+
   | tcp         | 443       | 443     | 0.0.0.0/0 |              |
   +-------------+-----------+---------+-----------+--------------+

   Despite only outputting the newly added rule, this operation is additive (both rules are created and enforced).

4. View all rules for the new security group, as follows:

   $ nova secgroup-list-rules global_http
   +-------------+-----------+---------+-----------+--------------+
   | IP Protocol | From Port | To Port | IP Range  | Source Group |
   +-------------+-----------+---------+-----------+--------------+
   | tcp         | 80        | 80      | 0.0.0.0/0 |              |
   | tcp         | 443       | 443     | 0.0.0.0/0 |              |
   +-------------+-----------+---------+-----------+--------------+

Procedure 3.3. Delete a security group

1. Ensure your system variables are set for the user and tenant for which you are deleting a security group for.

2. Delete the new security group, as follows:

   $ nova secgroup-delete GroupName

   For example:

   $ nova secgroup-delete global_http

Procedure 3.4. Create security group rules for a cluster of instances

Source Groups are a special, dynamic way of defining the CIDR of allowed sources. The user specifies a Source Group (Security Group name), and all the users' other Instances using the specified Source Group are selected dynamically. This alleviates the need for individual rules to allow each new member of the cluster.

1. Make sure to set the system variables for the user and tenant for which you are deleting a security group for.

2. Add a source group, as follows:

   $ nova secgroup-add-group-rule secGroupName source-group ip-protocol from-port to-port

   For example:

   $ nova secgroup-add-group-rule cluster global_http tcp 22 22

   The cluster rule allows ssh access from any other instance that uses the global_http group.

1. List the Compute services:

   $ nova service-list
   +------------------+----------+----------+---------+-------+----------------------------+-----------------+
   | Binary           | Host     | Zone     | Status  | State | Updated_at                 | Disabled Reason |
   +------------------+----------+----------+---------+-------+----------------------------+-----------------+
   | nova-conductor   | devstack | internal | enabled | up    | 2013-10-16T00:56:08.000000 | None            |
   | nova-cert        | devstack | internal | enabled | up    | 2013-10-16T00:56:09.000000 | None            |
   | nova-compute     | devstack | nova     | enabled | up    | 2013-10-16T00:56:07.000000 | None            |
   | nova-network     | devstack | internal | enabled | up    | 2013-10-16T00:56:06.000000 | None            |
   | nova-scheduler   | devstack | internal | enabled | up    | 2013-10-16T00:56:04.000000 | None            |
   | nova-consoleauth | devstack | internal | enabled | up    | 2013-10-16T00:56:07.000000 | None            |
   +------------------+----------+----------+---------+-------+----------------------------+-----------------+

2. Disable a nova service:

   $ nova service-disable localhost.localdomain nova-compute --reason 'trial log'
   +----------+--------------+----------+-------------------+
   | Host     | Binary       | Status   | Disabled Reason   |
   +----------+--------------+----------+-------------------+
   | devstack | nova-compute | disabled | Trial log         |
   +----------+--------------+----------+-------------------+

3. Check the service list:

   $ nova service-list
   +------------------+----------+----------+---------+-------+----------------------------+------------------+
   | Binary           | Host     | Zone     | Status   | State | Updated_at                 | Disabled Reason |
   +------------------+----------+----------+---------+-------+----------------------------+------------------+
   | nova-conductor   | devstack | internal | enabled  | up    | 2013-10-16T00:56:48.000000 | None            |
   | nova-cert        | devstack | internal | enabled  | up    | 2013-10-16T00:56:49.000000 | None            |
   | nova-compute     | devstack | nova     | disabled | up    | 2013-10-16T00:56:47.000000 | Trial log       |
   | nova-network     | devstack | internal | enabled  | up    | 2013-10-16T00:56:51.000000 | None            |
   | nova-scheduler   | devstack | internal | enabled  | up    | 2013-10-16T00:56:44.000000 | None            |
   | nova-consoleauth | devstack | internal | enabled  | up    | 2013-10-16T00:56:47.000000 | None            |
   +------------------+----------+----------+---------+-------+----------------------------+-----------------+

4. Enable the service:

   $ nova service-enable localhost.localdomain nova-compute
   +----------+--------------+---------+
   | Host     | Binary       | Status  |
   +----------+--------------+---------+
   | devstack | nova-compute | enabled |
   +----------+--------------+---------+

5. Check the service list:

   $ nova service-list
   +------------------+----------+----------+---------+-------+----------------------------+-----------------+
   | Binary           | Host     | Zone     | Status  | State | Updated_at                 | Disabled Reason |
   +------------------+----------+----------+---------+-------+----------------------------+-----------------+
   | nova-conductor   | devstack | internal | enabled | up    | 2013-10-16T00:57:08.000000 | None            |
   | nova-cert        | devstack | internal | enabled | up    | 2013-10-16T00:57:09.000000 | None            |
   | nova-compute     | devstack | nova     | enabled | up    | 2013-10-16T00:57:07.000000 | None            |
   | nova-network     | devstack | internal | enabled | up    | 2013-10-16T00:57:11.000000 | None            |
   | nova-scheduler   | devstack | internal | enabled | up    | 2013-10-16T00:57:14.000000 | None            |
   | nova-consoleauth | devstack | internal | enabled | up    | 2013-10-16T00:57:07.000000 | None            |
   +------------------+----------+----------+---------+-------+----------------------------+-----------------+

1. Write any buffered data to disk.

   For more information on taking snapshots, see the End User Guide at https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/.

2. List instances to get the server name:

   $ nova list
   +--------------------------------------+----------------------+--------+------------+-------------+------------------+
   | ID                                   | Name                 | Status | Task State | Power State | Networks         |
   +--------------------------------------+----------------------+--------+------------+-------------+------------------+
   | 84c6e57d-a6b1-44b6-81eb-fcb36afd31b5 | myCirrosServer       | ACTIVE | None       | Running     | private=10.0.0.3 |
   +--------------------------------------+----------------------+--------+------------+-------------+------------------+

   In this example, the server is named myCirrosServer.

3. Use this server to create a snapshot:

   $ nova image-create myCirrosServer myCirrosImg

   The command creates a qemu snapshot and automatically uploads the image to your repository. Only the tenant that creates the image has access to it.

4. Get details for your image to check its status:

   $ nova image-show myCirrosImg
   
   +----------------------+--------------------------------------+
   | Property             | Value                                |
   +----------------------+--------------------------------------+
   | OS-EXT-IMG-SIZE:size | 13147648                             |
   | created              | 2014-10-22T01:47:45Z                 |
   | id                   | 901d3823-2be1-4ce3-b9b4-56330d56fd45 |
   | minDisk              | 0                                    |
   | minRam               | 0                                    |
   | name                 | myCirrosImg                          |
   | progress             | 100                                  |
   | status               | ACTIVE                               |
   | updated              | 2014-10-22T01:49:25Z                 |
   +----------------------+--------------------------------------+

   The image status changes from SAVING to ACTIVE. Only the tenant who creates the image has access to it.

1. List flavors to show the ID and name, the amount of memory, the amount of disk space for the root partition and for the ephemeral partition, the swap, bandwidth cap, and the number of virtual CPUs for each flavor.

   $ nova flavor-list

2. To create a flavor, specify a name, ID, RAM size, disk size, and the number of VCPUs for the flavor, as follows:

   $ nova flavor-create FLAVOR_NAME FLAVOR_ID RAM_IN_MB ROOT_DISK_IN_GB NUMBER_OF_VCPUS

   Note

   The flavor ID is a number from 1 to 255 and cannot contain special characters or spaces.

   For a list of optional parameters, run this command:

   $ nova help flavor-create

3. After you create a flavor, assign it to a project by specifying the flavor name or ID and the tenant ID:

   $ nova flavor-access-add FLAVOR TENANT_ID

• Delete a specified flavor, as follows:

  $ nova flavor-delete FLAVOR_ID

1. To select the host where instances are launched, use the --availability_zone zone:host parameter on the nova boot command. For example:

   $ nova boot --image <uuid> --flavor m1.tiny --nic net-id=<networkID> --key_name test --availability-zone nova:server2

2. To specify which roles can launch an instance on a specified host, enable the create:forced_host option in the policy.json file. By default, this option is enabled for only the admin role.

3. To view the list of valid compute hosts, use the nova hypervisor-list command, as follows:

   $ nova hypervisor-list
   +----+---------------------+
   | ID | Hypervisor hostname |
   +----+---------------------+
   | 1  | server2             |
   | 2  | server3             |
   | 3  | server4             |
   +----+---------------------+

1. To list hosts and find a different host for the evacuated instance, run:

   $ nova host-list

2. Evacuate the instance. You can pass the instance password to the command by using the --password <pwd> option. If you do not specify a password, one is generated and printed after the command finishes successfully. The following command evacuates a server without shared storage from a host that is down to the specified host_b:

   $ nova evacuate evacuated_server_name host_b

   The instance is booted from a new disk, but preserves its configuration including its ID, name, uid, IP address, and so on. The command returns a password:

   +-----------+--------------+
   | Property  |    Value     |
   +-----------+--------------+
   | adminPass | kRAJpErnT4xZ |
   +-----------+--------------+

3. To preserve the user disk data on the evacuated server, deploy OpenStack Compute with a shared file system. To configure your system, see the End User Guide at https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/. In the following example, the password remains unchanged:

   $ nova evacuate evacuated_server_name host_b --on-shared-storage

1. This example assumes that logtest directory contains the following log files:

   Example 3.1. Example files

   2010-11-16-21_access.log
   2010-11-16-22_access.log
   2010-11-15-21_access.log
   2010-11-15-22_access.log

   Each file uses the following line format:

   Example 3.2. Log line format

   Nov 15 21:53:52 lucid64 proxy-server - 127.0.0.1 15/Nov/2010/22/53/52 DELETE /v1/AUTH_cd4f57824deb4248a533f2c28bf156d3/2eefc05599d44df38a7f18b0b42ffedd HTTP/1.0 204 - \
     - test%3Atester%2CAUTH_tkcdab3c6296e249d7b7e2454ee57266ff - - - txaba5984c-aac7-460e-b04b-afc43f0c6571 - 0.0432

2. Change into the logtest directory:

   $ cd logtest

3. Upload the log files into the logtest container:

   $ swift -A http://swift-auth.com:11000/v1.0 -U test:tester -K testing upload logtest *.log

   2010-11-16-21_access.log
   2010-11-16-22_access.log
   2010-11-15-21_access.log
   2010-11-15-22_access.log

4. Get statistics for the account:

   $ swift -A http://swift-auth.com:11000/v1.0 -U test:tester -K testing -q stat

   Account: AUTH_cd4f57824deb4248a533f2c28bf156d3
   Containers: 1
   Objects: 4
   Bytes: 5888268

5. Get statistics for the logtest container:

   $ swift -A http://swift-auth.com:11000/v1.0 -U test:tester -K testing stat logtest

   Account: AUTH_cd4f57824deb4248a533f2c28bf156d3
   Container: logtest
   Objects: 4
   Bytes: 5864468
   Read ACL:
   Write ACL:

6. List all objects in the logtest container:

   $ swift -A http:///swift-auth.com:11000/v1.0 -U test:tester -K testing list logtest

   2010-11-15-21_access.log
   2010-11-15-22_access.log
   2010-11-16-21_access.log
   2010-11-16-22_access.log

This example uses the -o —output option and a hyphen (-) to get information about an object.

Use the swift download command to download the object. On this command, stream the output to awk to break down requests by return code and the date 2200 on November 16th, 2010.

Using the log line format, find the request type in column 9 and the return code in column 12.

After awk processes the output, it pipes it to sort and uniq -c to sum up the number of occurrences for each request type and return code combination.

1. Download an object:

   $ swift -A http://swift-auth.com:11000/v1.0 -U test:tester -K testing \
    download -o - logtest 2010-11-16-22_access.log | awk ‘{ print $9”-“$12}’ | sort | uniq -c

   805 DELETE-204
   12 DELETE-404
   2 DELETE-409
   723 GET-200
   142 GET-204
   74 GET-206
   80 GET-304
   34 GET-401
   5 GET-403
   18 GET-404
   166 GET-412
   2 GET-416
   50 HEAD-200
   17 HEAD-204
   20 HEAD-401
   8 HEAD-404
   30 POST-202
   25 POST-204
   22 POST-400
   6 POST-404
   842 PUT-201
   2 PUT-202
   32 PUT-400
   4 PUT-403
   4 PUT-404
   2 PUT-411
   6 PUT-412
   6 PUT-413
   2 PUT-422
   8 PUT-499

2. Discover how many PUT requests are in each log file.

   Use a bash for loop with awk and swift with the -o —output option and a hyphen (-) to discover how many PUT requests are in each log file.

   Run the swift list command to list objects in the logtest container. Then, for each item in the list, run the swift download -o - command. Pipe the output into grep to filter the PUT requests. Finally, pipe into wc -l to count the lines.

   $ for f in `swift -A http://swift-auth.com:11000/v1.0 -U test:tester -K testing list logtest` ; \
    do echo -ne “PUTS - ” ; swift -A http://swift-auth.com:11000/v1.0 -U test:tester -K testing download -o - logtest $f | grep PUT | wc -l ; \
    done

   2010-11-15-21_access.log - PUTS - 402
   2010-11-15-22_access.log - PUTS - 1091
   2010-11-16-21_access.log - PUTS - 892
   2010-11-16-22_access.log - PUTS - 910

3. List the object names that begin with a specified string.

   Run the swift list -p 2010-11-15 command to list objects in the logtest container that begin with the 2010-11-15 string.

   For each item in the list, run the swift download -o - command.

   Pipe the output to grep and wc. Use the echo command to display the object name.

   $ for f in `swift -A http://swift-auth.com:11000/v1.0 -U test:tester -K testing list -p 2010-11-15 logtest` ; \
    do echo -ne “$f - PUTS - ” ; swift -A http://127.0.0.1:11000/v1.0 -U test:tester \
    -K testing download -o - logtest $f | grep PUT | wc -l ; \
    done

   2010-11-15-21_access.log - PUTS - 402
   2010-11-15-22_access.log - PUTS - 910