Anthony Kong's questions

I have turned on Polish in Cloudflare.

When the image is first download in chrome (Version 75.0.3770.142 (Official Build) (64-bit) in OSX), chrome dev console shows the following info:

* age: 12286
* cache-control: public, max-age=31556926
* cf-bgj: imgq:85
* cf-cache-status: HIT
* cf-polished: degrade=85, origSize=25843, status=vary_header_present
* cf-ray: 4fe67aba4d6b6549-SYD
* content-length: 5951
* content-type: image/jpeg
* date: Tue, 30 Jul 2019 09:59:21 GMT
* etag: "9314546c183b5befa64e265c89dc981f"
* expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
* expires: Wed, 29 Jul 2020 15:48:07 GMT
* last-modified: Thu, 11 Jul 2019 06:18:02 GMT
* server: cloudflare
* status: 200

Then when I access the same image in the same version but in incognito mode, I got the following:

* age: 21
* cache-control: public, max-age=31556926
* cf-bgj: imgq:85
* cf-cache-status: HIT
* cf-polished: qual=85, origFmt=jpeg, origSize=25843
* cf-ray: 4fe68b808803da4a-SYD
* content-disposition: inline; filename="image.webp"
* content-length: 3764
* content-type: image/webp
* date: Tue, 30 Jul 2019 10:10:49 GMT
* etag: "9314546c183b5befa64e265c89dc981f"
* expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
* expires: Wed, 29 Jul 2020 15:59:35 GMT
* last-modified: Thu, 11 Jul 2019 06:18:02 GMT
* server: cloudflare
* status: 200

What I do not understand is: If both access are HIT (i.e. there is cached images in CDN), why I got a webp second time around?

In my first request the header looks like this:

:authority: public.my-server.com
:method: GET
:path: /image.jpg
:scheme: https
accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3
accept-encoding: gzip, deflate, br
accept-language: en-GB,en-US;q=0.9,en;q=0.8,zh-TW;q=0.7,zh-CN;q=0.6,zh;q=0.5
cache-control: no-cache
cookie: __cfduid=xxxxx
pragma: no-cache
upgrade-insecure-requests: 1
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36

The second request is simply:

Origin: https://public.my-server.com
Referer: https://public.my-server.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36

Why the different images types?

I have an old AMI which used to run on a c4.large machine.

Since this class is not available an all AZ, I picked a c5.large to restore the image to.

However, when I run terraform to restore, I got this error message:

1 error(s) occurred:

• aws_instance.convertor: 1 error(s) occurred:

• aws_instance.convertor: Error launching source instance: InvalidParameterCombination: Enhanced networking with the Elastic Network Adapter (ENA) is required for the 'c5.large' instance type. Ensure that you are using an AMI that is enabled for ENA. status code: 400, request id: 7f32e7a1-c201-4db3-9f9e-6da4657ba9c8

How I can find which instance type can accept this old AMI? Or is there anything I can apply to the AMI to work with newer instance type?

Here is a terraform script I lifted from this repo

provider "aws" {
  region  = "${var.aws_region}"
  profile = "${var.aws_profile}"
}

##----------------------------
#     Get VPC Variables
##----------------------------

#-- Get VPC ID
data "aws_vpc" "selected" {
  tags = {
    Name = "${var.name_tag}"
  }
}

#-- Get Public Subnet List
data "aws_subnet_ids" "selected" {
  vpc_id = "${data.aws_vpc.selected.id}"

  tags = {
    Tier = "public"
  }
}

#--- Gets Security group with tag specified by var.name_tag
data "aws_security_group" "selected" {
  tags = {
    Name = "${var.name_tag}*"
  }
}

#--- Creates SSH key to provision server
module "ssh_key_pair" {
  source                = "git::https://github.com/cloudposse/terraform-aws-key-pair.git?ref=tags/0.3.2"
  namespace             = "example"
  stage                 = "dev"
  name                  = "${var.key_name}"
  ssh_public_key_path   = "${path.module}/secret"
  generate_ssh_key      = "true"
  private_key_extension = ".pem"
  public_key_extension  = ".pub"
}

#-- Grab the latest AMI built with packer - widows2016.json
data "aws_ami" "Windows_2016" {
  owners = [ "amazon", "microsoft" ]
  filter {
    name   = "is-public"
    values = ["false"]
  }

  filter {
    name   = "name"
    values = ["windows2016Server*"]
  }

  most_recent = true
}

#-- sets the user data script
data "template_file" "user_data" {
  template = "/scripts/user_data.ps1"
}


#---- Test Development Server
resource "aws_instance" "this" {
  ami                  = "${data.aws_ami.Windows_2016.image_id}"
  instance_type        = "${var.instance}"
  key_name             = "${module.ssh_key_pair.key_name}"
  subnet_id            = "${data.aws_subnet_ids.selected.ids[01]}"
  security_groups      = ["${data.aws_security_group.selected.id}"]
  user_data            = "${data.template_file.user_data.rendered}"
  iam_instance_profile = "${var.iam_role}"
  get_password_data    = "true"

  root_block_device {
    volume_type           = "${var.volume_type}"
    volume_size           = "${var.volume_size}"
    delete_on_termination = "true"
  }

  tags {
    "Name"    = "NEW_windows2016"
    "Role"    = "Dev"
  }

  #--- Copy ssh keys to S3 Bucket
  provisioner "local-exec" {
    command = "aws s3 cp ${path.module}/secret s3://PATHTOKEYPAIR/ --recursive"
  }

  #--- Deletes keys on destroy
  provisioner "local-exec" {
    when    = "destroy"
    command = "aws s3 rm 3://PATHTOKEYPAIR/${module.ssh_key_pair.key_name}.pem"
  }

  provisioner "local-exec" {
    when    = "destroy"
    command = "aws s3 rm s3://PATHTOKEYPAIR/${module.ssh_key_pair.key_name}.pub"
  }
}

When I tun terraform plan I got this error message:

Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

data.template_file.user_data: Refreshing state...

Error: Error refreshing state: 1 error(s) occurred:

* provider.aws: error validating provider credentials: error calling sts:GetCallerIdentity: NoCredentialProviders: no valid providers in chain. Deprecated.
    For verbose messaging see aws.Config.CredentialsChainVerboseErrors

Answers I found so far (e.g. Find out public ip address of the EC2 server) suggest using wget or curl to reach the server.

They are not useful for me because my ec2 instances are not reachable from the internet directly.

I have tried

aws ec2 --profile prod describe-instances --filters Name=instance-id,Values=i-00914683ababcba7eb1

But there are no IPs in the returned JSON result.

Which aws CLI command I can use to retrieve this info?

I have gone through all the steps and got to the last page.

However the 'upload' button is disabled.

I have checked the browser console and there is no error message. So it is unlikely a front end issue.

Why the upload button is disabled? Is it due to the number of files and/or total size?

I am trying to enable linux subsystem on a Windows Server 2016 on AWS EC2 by following these instructions https://docs.microsoft.com/en-us/windows/wsl/install-on-server

Here is the error message:

PS C:\Users\Administrator> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux
Enable-WindowsOptionalFeature : Feature name Microsoft-Windows-Subsystem-Linux is unknown.
At line:1 char:1
+ Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows- ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Enable-WindowsOptionalFeature], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand

My windows server is created based on an AWS ami.

How can I find out if my window server supports the linux subsystem? Is there anything I can do to enable the feature?

Update:

> systeminfo | Select-String "^OS Name","^OS Version"
OS Name:                   Microsoft Windows Server 2016 Datacenter
OS Version:                10.0.14393 N/A Build 14393

This is a nginx configuration

server {
    listen $PORT;

    location ~ ^/documents/(.*)$ {
        proxy_pass http://127.0.0.1:5000/$1;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }

    location = /favicon.ico {
        return 204;
        access_log    off;
        log_not_found off;
    }
}

There are two use cases of the url /documents/:

POST to /documents/ for some processing or

GET to /documents/ping used by AWS ELB as health check

In cloudwatch log I got heap of pings entries as a result

What is the easiest way to ask nginx not to log the ping?

I am trying to create a very simple cluster in sydney region.

It is a very straightforward setup. I specified the harddisk to be 60G. I want to have two ec2 instances in the cluster.

They show up as expected in ec2 panel.

However the ec2 instances are not showing up in the ecs cluster page:

1) Why It happens?

2) Is there any logging I can examine to find out the underlying problem?

The CMD of my dockerfile is this: ["python", "myproject/start_slide_server.py"]

However for this to work, I need to set the PYTHONPATH to /app, which is the parent directory of myproject

If I start the docker process and override CMD with bash, I can run the following

root@42e8998a8ff7:/app# export PYTHONPATH=.
root@42e8998a8ff7:/app# python myproject/start_slide_server.py
 * Running on http://0.0.0.0:8090/ (Press CTRL+C to quit)
 * Restarting with stat
 * Debugger is active!
 * Debugger PIN: 236-035-556

And it works as expected

Now I add the line

RUN export PYTHONPATH=/app

before

CMD ["python" , "myproject/start_slide_server.py"]

it just failed

Traceback (most recent call last):
  File "/app/myproject/start_slide_server.py", line 23, in <module>
    from myproject import env
ImportError: No module named myproject

It seems like the RUN line does not have any impact at all

I really do not want to define ENV at the dockercommand level because this PYTHONPATH will not change from one image to next.

How can I achieve this?

I can use the ENV directive

ENV PYTHONPATH /app

According to aws documentation, this is the command to install the aws-log agent:

sudo yum install -y awslogs

However since I am using ubuntu, I have to use apt-get. But the aws-log package is not available.

Is there an equivalent of the aws-log for ubuntu? If not, how can I install it?

My tasks are in PENDING status

That's what I can see in the events

There is not many information in the service events.

Here is the task definition in json

{
  "requiresAttributes": [
    {
      "value": null,
      "name": "com.amazonaws.ecs.capability.docker-remote-api.1.17",
      "targetId": null,
      "targetType": null
    },
    {
      "value": null,
      "name": "com.amazonaws.ecs.capability.docker-remote-api.1.18",
      "targetId": null,
      "targetType": null
    },
    {
      "value": null,
      "name": "com.amazonaws.ecs.capability.ecr-auth",
      "targetId": null,
      "targetType": null
    },
    {
      "value": null,
      "name": "com.amazonaws.ecs.capability.task-iam-role",
      "targetId": null,
      "targetType": null
    },
    {
      "value": null,
      "name": "com.amazonaws.ecs.capability.logging-driver.awslogs",
      "targetId": null,
      "targetType": null
    },
    {
      "value": null,
      "name": "com.amazonaws.ecs.capability.task-iam-role-network-host",
      "targetId": null,
      "targetType": null
    },
    {
      "value": null,
      "name": "com.amazonaws.ecs.capability.docker-remote-api.1.19",
      "targetId": null,
      "targetType": null
    }
  ],
  "taskDefinitionArn": "arn:aws:ecs:ap-southeast-2:1234567890:task-definition/SQ1-queuetest:1",
  "networkMode": "host",
  "status": "ACTIVE",
  "revision": 1,
  "taskRoleArn": "arn:aws:iam::1234567890:role/play-ecs",
  "containerDefinitions": [
    {
      "volumesFrom": [],
      "memory": 256,
      "extraHosts": null,
      "dnsServers": null,
      "disableNetworking": null,
      "dnsSearchDomains": null,
      "portMappings": [],
      "hostname": null,
      "essential": true,
      "entryPoint": null,
      "mountPoints": [],
      "name": "sq1",
      "ulimits": null,
      "dockerSecurityOptions": null,
      "environment": [
        {
          "name": "ENV",
          "value": "test"
        }
      ],
      "links": null,
      "workingDirectory": "/app/src/",
      "readonlyRootFilesystem": null,
      "image": "1234567890.dkr.ecr.ap-southeast-2.amazonaws.com/simplequeue:latest",
      "command": [
        "python /app/src/main.py"
      ],
      "user": null,
      "dockerLabels": null,
      "logConfiguration": {
        "logDriver": "awslogs",
        "options": {
          "awslogs-group": "simplequeue",
          "awslogs-region": "ap-southeast-2",
          "awslogs-stream-prefix": "sq1"
        }
      },
      "cpu": 512,
      "privileged": null,
      "memoryReservation": null
    }
  ],
  "placementConstraints": [],
  "volumes": [],
  "family": "SQ1-queuetest"
}

How can I find out more why the task is failing to start?

But I am getting this error:

Failed registering Scalable Target

Scalable Target could not register scalable target: 1 validation error detected: Value '' at 'roleARN' failed to satisfy constraint: Member must have length greater than or equal to 1 (Service: AWSApplicationAutoScaling; Status Code: 400; Error Code: ValidationException; Request ID: dff37db1-4be5-11e7-8739-df4df785c602)

I really don't know how to resolve this issue.

I have used an account play-admin to create all these cluster and service. It has the following rights:

The task is run using this role play-ecs:

I have also put in the trust relationship to this role:

My Question:

What permission do I need to grant to get the autoscaling to work? What confuse me greatly is in the message: "Member must have length greater than or equal to 1 ", what does this member refer to? The IAM account I used to create this autoscaling? The role of the task? Or the newly created 'IAM autoscale role' (see the following screen shot)? If it is the last one, it seems like it is beyond my control.

*This screensot shows that a step IAM Autoscale role: <create_new> is executed by ECS

I am trying to set up a ECS but so far I have encountered a few permission issue for which I have created some questions on this forum already.

I think I am stuck so far because honestly I cannot find out all these role requirements in one place concisely.

It seems like I need to define at least two roles:

1) ECS container http://docs.aws.amazon.com/AmazonECS/latest/developerguide/instance_IAM_role.html

2) ECS task http://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-iam-roles.html#enable_task_iam_roles

Is it correct?

Did I miss out anything? Is there any special IAM requirement?

In a typical dockerfile, there is usually this line From ubuntu:16.04 which enables pulling an image from docker repository.

Now I have built my own image repository:

The repositiory URI is: 1234567890.dkr.ecr.us-west-2.amazonaws.com/mycompany

As seen in the above screenshot, I pushed an image to the server.

I run the following to ensure I have login to the ecr

> `aws ecr get-login --region us-west-2`
Flag --email has been deprecated, will be removed in 1.14.
Login Succeeded

ECR login completes without error. Then I tried to build a new image:

> docker build -t rtf-converter . -f Dockerfile-rtf-converter 
Sending build context to Docker daemon 790.1 MB
Step 1/2 : FROM mycompany:latest
repository mycompany not found: does not exist or no pull access

Here is the content of the Dockerfile

FROM mycompany:latest
RUN apt-get install chef-zero

What is the right way to specify the repository properly in the FROM statement?

I am particularly confused by labels. What is a good convention of labeling?

This is my Dockerfile

FROM ubuntu:16.04
RUN apt-get update -y && apt-get install -y \
  git \
  python \
  python-pip

After the docker image is created, I login and try to setup a cron job for testing. To my surprise, cron and crontab are not present.

# ls 
app  bin  boot  dev  etc  home  lib  lib64  media  mnt  opt  proc  
root  run  sbin  srv  sys  tmp  usr  var
# crontab -l
/bin/sh: 6: crontab: not found
# crontab -l
/bin/sh: 7: crontab: not found
# crontab -l
/bin/sh: 10: crontab: not found
# cron
/bin/sh: 11: cron: not found

But I expect cron to be present in an ubuntu image. Did I pick a wrong image or is there anything I need to do to enable cron?

I am adding a new google app engine project and trying to map it to a subdomain.

I have already created a CNAME which maps newmachine.mycompany.com to newproject.appsport.com, and I am able to use it in 'App Engine' -> 'Settings' ->'Custom domains'.

But once the mapping is finsihed, the same screen shows the following messages:

Configure resource records on your domain registrar
Have your domain registrar add the following resource records for mycompany.com:
Type    Data    Alias
A   215.234.32.21   
A   215.234.34.21   
A   215.234.36.21   
A   215.234.38.21   
AAAA    1997:2340:4801:32::15   
AAAA    1997:2340:4801:34::15   
AAAA    1997:2340:4801:36::15   
AAAA    1997:2340:4801:38::15   
CNAME   ghs.googlehosted.com    newmachine

I haven't seen this message before. As a matter of face, no such A and AAAA were created for other existing GAE projects.

My questions are:

1. What is the implication of NOT adding these records to my DNS server?

2. What purpose do they serve? Is it simply to provide a reverse IP lookup?

I have successfully set up a load balancer in google cloud platform

If I use the IP as shown in the image, I can test and verify that the set up is working as I planned.

Now I would like to map a domain name to the IP. I want to use www.mycompany.com. I have already created a A record in my DNS to point www to 1.2.3.4. However the domain name gives a 404 error.

I am sure I need to associate this new domain name to the IP address.

There is no obvious place to do it in load balanceing or external IP addresses screen.

Where can I do it?

Background: I am trying to set up an instance group in Google cloud platform. The instance group consists a number of nginx instances whose job is simply to redirect incoming https traffic to an external site. If the incoming traffic is http, it will be convert to https.

For the instance group to work, it must respond to a health check request (in either http or https protocol) and return 200.

The problem I have is how to define such a nginx configuration.

This is my first cut. It only handles the redirection

    server {
        listen 80;
        listen 443 ssl;
        ssl on;
        ssl_certificate /etc/nginx/ssl/examples.pem;
        ssl_certificate_key /etc/nginx/ssl/examples.key;
        server_name incoming.examples.com;
        return 301 https://target.examples.com$request_uri;
    }

I set the health check url to be '/_check' with http protocol. This is my first attempt:

    server {
        listen 80;

        location /_check {
            return 200 'no content';
        }

        listen 443 ssl;
        ssl on;
        ssl_certificate /etc/nginx/ssl/examples.pem;
        ssl_certificate_key /etc/nginx/ssl/examples.key;
        server_name incoming.examples.com;
        return 301 https://target.examples.com$request_uri;
    }

The nginx server responds with a 404.

Then I attempted to move location to another server definition:

    server {
        location /_check {
            return 200 'no content';
        }
        listen 80;
    }

    server {
        listen 80;
        listen 443 ssl;
        ssl on;
        ssl_certificate /etc/nginx/ssl/examples.pem;
        ssl_certificate_key /etc/nginx/ssl/examples.key;
        server_name incoming.examples.com;
        return 301 https://target.examples.com$request_uri;
    }

It gives me the same result. This is what I see in the access log.

130.211.3.85 - - [18/Jan/2017:08:41:25 +0000] "GET /_check HTTP/1.1" 404 168 "-" "GoogleHC/1.0"
130.211.3.81 - - [18/Jan/2017:08:41:29 +0000] "GET /_check HTTP/1.1" 404 168 "-" "GoogleHC/1.0"
130.211.1.249 - - [18/Jan/2017:08:41:30 +0000] "GET /_check HTTP/1.1" 404 168 "-" "GoogleHC/1.0"
130.211.3.85 - - [18/Jan/2017:08:41:30 +0000] "GET /_check HTTP/1.1" 404 168 "-" "GoogleHC/1.0"
130.211.3.81 - - [18/Jan/2017:08:41:34 +0000] "GET /_check HTTP/1.1" 404 168 "-" "GoogleHC/1.0"
130.211.1.249 - - [18/Jan/2017:08:41:35 +0000] "GET /_check HTTP/1.1" 404 168 "-" "GoogleHC/1.0"
130.211.3.85 - - [18/Jan/2017:08:41:35 +0000] "GET /_check HTTP/1.1" 404 168 "-" "GoogleHC/1.0"
130.211.3.81 - - [18/Jan/2017:08:41:39 +0000] "GET /_check HTTP/1.1" 404 168 "-" "GoogleHC/1.0"
130.211.1.249 - - [18/Jan/2017:08:41:40 +0000] "GET /_check HTTP/1.1" 404 168 "-" "GoogleHC/1.0

If I revert the change to my first attempt, and change the health check to use https (as in the following screenshot),

I get 301 instead. It seems to me the url _check is overridden by the redirction rule.

My question: How can I modify the nginx to meet the requirement?

I would like to be able to fire a task before a windows server 2012 is reboot or shutdown.

I can see task scheduler supports an 'on startup' trigger. Unfortunately there is similar event for reboot or restart. Is there anyway I can achieve the my goal?

I have created an instance of ubuntu VM in VirtualBox. At the beginning I have only allocated 7GB for the storage and the VM has now run out of space.

First I added another 8GB (/dev/sdb) to the VM via VirtualBox frontend. I then set up the following partitions:

$ sudo fdisk -l /dev/sdb

Disk /dev/sdb: 8589 MB, 8589934592 bytes
40 heads, 1 sectors/track, 419430 cylinders, total 16777216 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x076b5690

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048    16777215     8387584    5  Extended
/dev/sdb5            4096    16777215     8386560   8e  Linux LVM

Then I ran the following commands to expand the VG.

  sudo pvcreate /dev/sdb5
  sudo vgextend ubuntudevbox2 /dev/sdb5
  sudo lvextend 100% /dev/ubuntudevbox2/root
  lvextend --help
  sudo lvextend -l 100%FREE /dev/ubuntudevbox2/root
  sudo lvextend -r -l 100%FREE /dev/ubuntudevbox2/root
  sudo resize2fs  /dev/mapper/ubuntudevbox2-root

I would have expected the size of / to expand to 16Gb. However df reports that

$ df -h
Filesystem                      Size  Used Avail Use% Mounted on
/dev/mapper/ubuntudevbox2-root  8.0G  6.9G  680M  92% /

the root mount has only increased to 8G

Here is the VG information

$ sudo vgdisplay ubuntudevbox2
[sudo] password for antkong: 
  --- Volume group ---
  VG Name               ubuntudevbox2
  System ID             
  Format                lvm2
  Metadata Areas        2
  Metadata Sequence No  5
  VG Access             read/write
  VG Status             resizable
  MAX LV                0
  Cur LV                2
  Open LV               2
  Max PV                0
  Cur PV                2
  Act PV                2
  VG Size               15.75 GiB
  PE Size               4.00 MiB
  Total PE              4033
  Alloc PE / Size       2182 / 8.52 GiB
  Free  PE / Size       1851 / 7.23 GiB
  VG UUID               ZV6VAi-qkxC-KnKz-1LHg-nfLB-afSI-mVpIPv

Why I did not get the full 8Gb additional space?

Additional information 1: I have run mkfs -t ext5 /dev/sdb5 right after using fdisk to add new partition. Can it cause the failure?

Additional information 2:

$ uname -a
Linux ubuntudevbox2 3.5.0-27-generic #46-Ubuntu SMP Mon Mar 25 19:58:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

lvdisplay output:

$ sudo lvdisplay

  --- Logical volume ---
  LV Path                /dev/ubuntudevbox2/root
  LV Name                root
  VG Name                ubuntudevbox2
  LV UUID                V1Qq0f-qKJR-UTf5-4tjM-ycoY-1J5L-mJQ2Fy
  LV Write Access        read/write
  LV Creation host, time ubuntudevbox2, 2013-03-29 12:18:26 +1100
  LV Status              available
  # open                 1
  LV Size                8.03 GiB
  Current LE             2055
  Segments               3
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           252:0

  --- Logical volume ---
  LV Path                /dev/ubuntudevbox2/swap_1
  LV Name                swap_1
  VG Name                ubuntudevbox2
  LV UUID                LbvPFE-j3GO-oaF1-HQV3-a2r5-HTfy-YrhQve
  LV Write Access        read/write
  LV Creation host, time ubuntudevbox2, 2013-03-29 12:18:29 +1100
  LV Status              available
  # open                 2
  LV Size                508.00 MiB
  Current LE             127
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto
  - currently set to     256
  Block device           252:1