New EC2 Korea region

Bug #1530957 reported by Cheryl Jennings
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Martin Packman
goamz
Fix Released
High
Martin Packman
juju-core
Fix Released
High
Martin Packman
1.25
Fix Released
High
Martin Packman
juju-release-tools
Fix Released
High
Martin Packman

Bug Description

There is a new Korea region coming in "early 2016" that we will need to add support for: https://aws.amazon.com/blogs/aws/next-stop-korea/

Name, supported instance types, and pricing are all still TBA.

Revision history for this message
Curtis Hovey (sinzui) wrote :
Changed in juju-release-tools:
status: New → Triaged
importance: Undecided → High
Changed in juju-core:
status: New → Triaged
importance: Undecided → High
milestone: none → 2.0-beta1
Revision history for this message
Haw Loeung (hloeung) wrote :

Is it possible to also have support for the new EC2 Korea region backported to 1.24.7-trusty-amd64?

We need this to bring up archive mirrors.

Revision history for this message
Junien Fridrick (axino) wrote :

The new region (ap-northeast-2) is available for public use.

Revision history for this message
Cheryl Jennings (cherylj) wrote :
Changed in juju-core:
assignee: nobody → Martin Packman (gz)
Revision history for this message
Robert C Jennings (rcj) wrote :

Images are indexed in simplestreams as of today. Daily images from the past 30 days and all release images for supported suites were sync'ed to the region on Dec 30th. I am still working on publication of images as part of our normal publishing (this region lacks 32-bit so new assumptions, new code) so this region will not have the current daily for a bit longer.

Revision history for this message
Robert C Jennings (rcj) wrote :

Which is to say (Comment #6) that work on the AWS provider to support this region should be unblocked.

Revision history for this message
Martin Packman (gz) wrote :

Change for amz.v3 proposed:

<https://github.com/go-amz/amz/pull/65>

Changed in goamz:
assignee: nobody → Martin Packman (gz)
importance: Undecided → High
status: New → In Progress
Curtis Hovey (sinzui)
Changed in juju-release-tools:
assignee: nobody → Martin Packman (gz)
status: Triaged → Fix Released
Revision history for this message
Martin Packman (gz) wrote :

Changes for juju landed as well:

1.25 <https://github.com/juju/juju/pull/4171>
master <https://github.com/juju/juju/pull/4244>

Streams work also done, everything should be up and working now.

Changed in juju-core:
status: Triaged → Fix Committed
Changed in goamz:
status: In Progress → Fix Released
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
affects: juju-core → juju
Changed in juju:
milestone: 2.0-beta1 → none
milestone: none → 2.0-beta1
Changed in juju-core:
assignee: nobody → Martin Packman (gz)
importance: Undecided → High
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.