Comment 3 for bug 1625243

@anastaia, you are confused. These *new* stream are not CI's streams. As an author of streams. I am very aware about setting custom streams for tests. For the test of the proposed streams, I had to write and publish the streams myself. The streams you investigated last week are not related to these streams. CI is not involved.

Since my last comment, index.sjson has been update to include racsapace, but juju still does not recognise the clouds because the endpoints used by Juju (also published here)
    http://streams.canonical.com/juju/public-clouds.syaml
are not the endpoints in the CPC streams
    https://cloud-images.ubuntu.com/releases/streams/v1/index.sjson

Juju, like other simplestream apps matches the cloud by endpoint. CPC uses this form
    https://syd.images.api.rackspacecloud.com/v2
Juju uses
    https://identity.api.rackspacecloud.com/v2.0

You can verify this issue with an RC1 candidate.
    juju --debug bootstrap rax-cpc rackspace/syd

03:52:53 DEBUG juju.environs.bootstrap bootstrap.go:569 found 0 image metadata in default cloud images
03:52:54 DEBUG juju.environs.simplestreams simplestreams.go:454 skipping index "http://cloud-images.ubuntu.com/releases/streams/v1/index.sjson" because of missing information: index file has no data for cloud {SYD https://identity.api.rackspacecloud.com/v2.0} not found
03:52:54 DEBUG juju.environs.bootstrap bootstrap.go:565 ignoring image metadata in default ubuntu cloud images: index file has no data for cloud {SYD https://identity.api.rackspacecloud.com/v2.0} not found
03:52:54 DEBUG juju.environs.bootstrap bootstrap.go:573 found 0 image metadata from all image data sources
...
03:52:57 ERROR cmd supercommand.go:458 failed to bootstrap model: no image metadata found

You can be very clear about which streams you want juju to check by setting image-metadata-url to the official streams and switching providers to observe how juju reads the clouds

    juju --debug bootstrap rax-cpc rackspace/syd --config image-metadata-url=http://cloud-images.ubuntu.com/releases
vs.
    juju --debug bootstrap gce-cpc google/us-central1 --config image-metadata-url=http://cloud-images.ubuntu.com/releases

^ rackspace 0, google 6.

The two options forward are for CPC to change endpoints at cloud-images, or for juju to update its own file
    https://github.com/juju/juju/blob/master/cloud/fallback-public-cloud.yaml

^ I favour juju switching to what the CPC/cloud wants to use.
    https://<region>.images.api.rackspacecloud.com/v2