Update default environment.yaml for Azure to use Precise for default-series

[Antonio Rosales]

The default boilerplate environment.yaml created by either juju init or juju generate-config sets the default-series set to Saucy as that was needed in development. An SRU (cloud-init and walinux agent) to enable Juju on Azure on Precise has landed in Ubuntu and daily images of Precise as of today are being published in Azure. Thus, this bug is to update the boilerplate config in the Azure stanza to use "default-series: precise."

Current:
  azure:
    type: azure
. . .
    default-series: saucy

Needed:
  azure:
    type: azure
. . .
    default-series: precise

-thanks,
Antonio

[Antonio Rosales (arosales)]

I am confirming if the image-stream should be set to "released" also. I'll post here once I have confirmation.

-thanks,
Antonio

[John A Meinel (jameinel)]

This is trivial to change, the only reason it isn't done yet was because juju didn't actually work with Precise on Azure.

If we can confirm that this now works, it would be great to get it into 1.13.3

[Dave Cheney (dave-cheney)]

@axw, if you can't confirm this works by the close of your day, please move it to the 1.15.0 milestone.

[Andrew Wilkins (axwalk)]

I've just tried:
    image-stream: released
    default-series: precise

... and it says it can't find a suitable OS image.

I then tried:
    image-stream: daily
    default-series: precise

... and it won't allow me to SSH in.

I've confirmed daily/saucy still works in my env.

[Antonio Rosales (arosales)]

Couple of comments.

This is a blocker for 1.13.3 as it defaults Azure users to a non-optimal config. If we have simple streams defaulting to saucy then there won't be a lot of choices for charms to use. I have confirmed with Ben Howard (utlemming) that the SRU for cloud-init and walinux agent fixes have landed in Ubuntu, and are being replicated to Azure image gallery.

Per the comment:
   # Pick a simplestreams stream to select OS images from: daily or released
    # images, or any other stream available on simplestreams. Leave blank for
    # released images.
and the stream data:
    http://cloud-images.ubuntu.com/releases/streams/v1/com.ubuntu.cloud:released:download.json

I think the "image-stream" should be left blank or set to "releases" in order to get the released stream.

I am giving this syntax a try now although the precise image(with cloud-init and walinux agent fixes) needed is still being replicated to the Azure gallery.

-Thanks,
Antonio

[Antonio Rosales (arosales)]

Leaving "image-stream:" blank gives me:
error: image-stream: expected string, got nothing

Thus, that comment needs to be removed or fixed in code. Trying with:
  image-stream: releases

-thanks,
Antonio

[Dave Cheney (dave-cheney)]

Hi Antonio,

The plan is to branch 1.14 as soon as possible, then we can address issues like this on the branch. Axw tested azure with precise yesterday and found it non functional, I asked him to move this bug to 1.15.0 so that it would not block the branch.

Ideally so etching clearer would have been to move it to 1.14 series, or 1.14.1 but neither of those existed on Friday.

Does that sound sane?

On 31/08/2013, at 9:33, Antonio Rosales <email address hidden> wrote:

> Couple of comments.
>
> This is a blocker for 1.13.3 as it defaults Azure users to a non-optimal
> config. If we have simple streams defaulting to saucy then there won't
> be a lot of choices for charms to use. I have confirmed with Ben Howard
> (utlemming) that the SRU for cloud-init and walinux agent fixes have
> landed in Ubuntu, and are being replicated to Azure image gallery.
>
>
> Per the comment:
> # Pick a simplestreams stream to select OS images from: daily or released
> # images, or any other stream available on simplestreams. Leave blank for
> # released images.
> and the stream data:
> http://cloud-images.ubuntu.com/releases/streams/v1/com.ubuntu.cloud:released:download.json
>
> I think the "image-stream" should be left blank or set to "releases" in
> order to get the released stream.
>
> I am giving this syntax a try now although the precise image(with cloud-
> init and walinux agent fixes) needed is still being replicated to the
> Azure gallery.
>
> -Thanks,
> Antonio
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1218329
>
> Title:
> Update default environment.yaml for Azure to use Precise for default-
> series
>
> Status in juju-core:
> Triaged
>
> Bug description:
> The default boilerplate environment.yaml created by either juju init
> or juju generate-config sets the default-series set to Saucy as that
> was needed in development. An SRU (cloud-init and walinux agent) to
> enable Juju on Azure on Precise has landed in Ubuntu and daily images
> of Precise as of today are being published in Azure. Thus, this bug is
> to update the boilerplate config in the Azure stanza to use "default-
> series: precise."
>
> Current:
> azure:
> type: azure
> . . .
> default-series: saucy
>
> Needed:
> azure:
> type: azure
> . . .
> default-series: precise
>
> -thanks,
> Antonio
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1218329/+subscriptions

[Antonio Rosales (arosales)]

My second hypothesis on "image-stream" being "releases" is also incorrect as http://cloud-images.ubuntu.com/releases/streams/v1/index.sjson is looking for "released." Specifically:

Per comment 4:
    image-stream: daily
    default-series: precise

Is expected to fail on ssh as these images don't have the cloud-init and walinux agent fixes in them.

Per comment 4:
    image-stream: released
    default-series: precise

should at least be able to bootstrap. . .

My suggestion is we hold off on cutting a 1.13.3 devel release until we can sort why
    image-stream: released
    default-series: precise
is not working with the latest Azure precise images (once they have finished replicating on Monay, US time).

-thanks,
Antonio

[Antonio Rosales (arosales)]

fyi I have a branch that updates the Azure boilerplate template at:
  lp:~a.rosales/juju-core/update-azure-boilerplate

[Antonio Rosales (arosales)]

    image-stream: released
    default-series: precise
Fails due to:
  https://bugs.launchpad.net/juju-core/+bug/1219123

Basically Juju does not parse "released" simple streams correctly.

It is important to use "released" streams as there is no warranty or QA on daily images.

[Antonio Rosales (arosales)]

I can lbox propose my branch once I get a confirmation here to go ahead.

-thanks,
Antonio

[John A Meinel (jameinel)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-08-31 4:30, Antonio Rosales wrote:
> I can lbox propose my branch once I get a confirmation here to go
> ahead.
>
> -thanks, Antonio
>

You might as well propose it, we can hold of landing it until the
'released' bug is fixed.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlIiPmkACgkQJdeBCYSNAAMs0QCfRAv2QsAjr8BUpTAAg5Txz2Us
euoAoJVAy0kZdIrNaFGPXDWV5P0TTRR4
=AAid
-----END PGP SIGNATURE-----

[John A Meinel (jameinel)]

Did you try
  image-stream: ""

From what I can read of the code, "" means to use the released stream.

[Antonio Rosales (arosales)]

fwiw the Azure boilerplate I would suggest is at:
lp:~a.rosales/juju-core/update-azure-boilerplate

Only change is to comment out the "image-stream" and and in a comment stating what the default is.

-thanks,
Antonio