On Wed, Oct 24, 2018, 3:38 AM David Osborne wrote:
> Thanks Martin,
>
> We of course are in the process of migrating on from Jessie but due to LTS
> the timescales were deliberately left quite loose.
>
> Re your timeline email - I think it's a good idea having such a timeline
> prominently
Thanks Martin,
We of course are in the process of migrating on from Jessie but due to LTS
the timescales were deliberately left quite loose.
Re your timeline email - I think it's a good idea having such a timeline
prominently reiterated. It certainly hadn't occurred to me that support for
On Tue, Oct 23, 2018 at 10:04:33AM +0200, Thomas Goirand wrote:
> >> I object because, at the 2018 Debian Cloud Sprint, we collectively
> >> decided that we were not offering Debian LTS Cloud Images. Are we
> >> changing our decision? I'd like to see collective decision making, not
> >> one-offs
On Tue, Oct 23, 2018 at 11:51:26AM +0100, David Osborne wrote:
>Thank you... so the amis themselves should remain indefinitely?
I'd expect "release" AMIs to remain indefinitely, yes. There's strong
precident for this within AWS in general; it's part of the pledge to not
break users. For
On Tue, Oct 23, 2018, 6:17 AM Martin Zobel-Helas wrote:
> David,
>
> Also from a user’s perspective i would like to hear your feedback on the
> mail I wrote earlier today to the cloud list... Be aware that none of the
> timeline in this mail is written into stone yet. It is just a proposal.
>
>
David,
Also from a user’s perspective i would like to hear your feedback on the mail I
wrote earlier today to the cloud list... Be aware that none of the timeline in
this mail is written into stone yet. It is just a proposal.
Best regards,
Martin
> Am 23.10.2018 um 13:14 schrieb Martin
Hi David,
My understanding is that removing the images from the vendors market places is
to make the images less easy discoverable and to discourage users from spinning
new instances from an old image type. I don’t know the exact details for AWS
but my guess is those AMI IDs will NOT remain
Thank you... so the amis themselves should remain indefinitely?
--
David
On Tue, 23 Oct 2018 at 11:47, Martin Zobel-Helas wrote:
>
>
> From my understanding Noah only removed the links from the market place,
> but did not remove the images from the storage. This means by knowing the
> image
Hi David,
> Am 23.10.2018 um 12:09 schrieb David Osborne :
>
> We are among the population of users who are still using the Jessie AMIs and,
> until reading this, had planned to until 2020 due to LTS.
>
> We often have to rebuild instances on top of your Jessie AMIs since there are
> various
We are among the population of users who are still using the Jessie AMIs
and, until reading this, had planned to until 2020 due to LTS.
We often have to rebuild instances on top of your Jessie AMIs since there
are various hurdles we still have to clear before Stretch will be an option
for our
On Sun, 21 Oct 2018, Noah Meyerhans wrote:
> I'm sure a lot of it is a matter of perception, but the level of
> integration of LTS with the stable lifecycle does not seem as deep as
> someone familiar with Debian stable might expect it to be. For example,
> security announcements being published
On Mon, 22 Oct 2018, Noah Meyerhans wrote:
> clear user demand for it, or we wouldn't be having this conversation. So
> I think we're better served by figuring out how to make LTS work (in
> cloud environments and more generally) than by trying to figure out how
> we can say no.
+1
> Is there
On 10/22/18 8:10 PM, Noah Meyerhans wrote:
> On Mon, Oct 22, 2018 at 05:52:15PM +, Luca Filipozzi wrote:
>> I object because, at the 2018 Debian Cloud Sprint, we collectively
>> decided that we were not offering Debian LTS Cloud Images. Are we
>> changing our decision? I'd like to see
On Mon, Oct 22, 2018 at 07:12:54PM +, Luca Filipozzi wrote:
> Is this true: the goal of the Debian Cloud Team is to make roughly equievalent
> Debian Cloud Images for the various cloud providers so that
> Debian users have a consistent (to the degree possible) experience with
> Debian in each
On Mon, Oct 22, 2018 at 11:10:57AM -0700, Noah Meyerhans wrote:
> On Mon, Oct 22, 2018 at 05:52:15PM +, Luca Filipozzi wrote:
> > I object because, at the 2018 Debian Cloud Sprint, we collectively
> > decided that we were not offering Debian LTS Cloud Images. Are we
> > changing our decision?
On Mon, Oct 22, 2018 at 11:34:14AM -0700, Larry Fletcher wrote:
> So far the security updates for the Jessie kernel have stayed in the 3.16.*
> range, and I doubt if that will change.
Try apt-cache policy linux-image-4.9-amd64
> A few weeks ago I ran a test "dist-upgrade" to Stretch and was
On 10/21/2018 07:53 PM, Noah Meyerhans wrote:
Lack of integration with packages.debian.org and incomplete coverage of
the archive also present problems. For exaple, despite the existence of
DLA 1531, I cannot find evidence of a 4.9 kernel for jessie on
packages.debian.org except in
On Mon, Oct 22, 2018 at 10:01:44AM -0700, Noah Meyerhans wrote:
> What do people think? Does anybody have particularly strong objections
> to putting the AWS Marketplace listing for jessie back up? I think we
> may have been hasty with the EOL of the jessie images, at least on AWS.
The line
On Mon, Oct 22, 2018 at 05:52:15PM +, Luca Filipozzi wrote:
> I object because, at the 2018 Debian Cloud Sprint, we collectively
> decided that we were not offering Debian LTS Cloud Images. Are we
> changing our decision? I'd like to see collective decision making, not
> one-offs for each
On Sun, Oct 14, 2018 at 10:53:19AM -0700, Noah Meyerhans wrote:
> I've submitted requests to the AWS Marketplace to remove our Jessie
> listings. They haven't yet acted on these requests, but they should do
> so in the coming week.
It sounds like the removal of the jessie listings has taken
On Fri, Oct 19, 2018 at 04:14:47PM +0200, Raphael Hertzog wrote:
> > The main thing: concerns were raised by several of the cloud platforms
> > people that LTS security doesn't seem to be working very well. They're
> > not seeing fixes happening for known issues, and so at the moment they
> >
Hi,
> Am 21.10.2018 um 17:02 schrieb Thomas Goirand :
>
> Building the OpenStack Debian cloud image is super simple. It needs
> running the script provided by the openstack-debian-images package.
And testing of those images.
Best regards,
Martin
On 10/19/18 4:14 PM, Raphael Hertzog wrote:
> On Fri, 19 Oct 2018, Steve McIntyre wrote:
>> The main thing: concerns were raised by several of the cloud platforms
>> people that LTS security doesn't seem to be working very well. They're
>> not seeing fixes happening for known issues, and so at the
On 2018-10-19 16:14:47, Raphael Hertzog wrote:
> On Fri, 19 Oct 2018, Steve McIntyre wrote:
> > The main thing: concerns were raised by several of the cloud platforms
> > people that LTS security doesn't seem to be working very well. They're
> > not seeing fixes happening for known issues, and so
On Fri, Oct 19, 2018 at 04:14:47PM +0200, Raphael Hertzog wrote:
>On Fri, 19 Oct 2018, Steve McIntyre wrote:
>> The main thing: concerns were raised by several of the cloud platforms
>> people that LTS security doesn't seem to be working very well. They're
>> not seeing fixes happening for known
On Fri, 19 Oct 2018, Steve McIntyre wrote:
> The main thing: concerns were raised by several of the cloud platforms
> people that LTS security doesn't seem to be working very well. They're
> not seeing fixes happening for known issues, and so at the moment they
> don't have trust in the process.
On Fri, Oct 19, 2018 at 11:17:05AM +0200, Bastian Blank wrote:
>On Fri, Oct 19, 2018 at 09:09:55AM +0200, Raphael Hertzog wrote:
>> On Sun, 14 Oct 2018, Steve McIntyre wrote:
>> > One of our (many!) discussion topics at our sprint last week was
>> > announcing the end of support for our published
On Fri, 19 Oct 2018, Bastian Blank wrote:
> > Are you unaware of Debian LTS or are there any reasons why the security
> > support provided by that official Debian team is not suitable in the
> > context of cloud images?
>
> Please search for LTS in the notes of our meeting last week:
>
Hi Raphael
On Fri, Oct 19, 2018 at 09:09:55AM +0200, Raphael Hertzog wrote:
> On Sun, 14 Oct 2018, Steve McIntyre wrote:
> > One of our (many!) discussion topics at our sprint last week was
> > announcing the end of support for our published Jessie (Debian 8.x)
> > images. We strongly recommend
Hi Steve,
On Sun, 14 Oct 2018, Steve McIntyre wrote:
> One of our (many!) discussion topics at our sprint last week was
> announcing the end of support for our published Jessie (Debian 8.x)
> images. We strongly recommend that all our existing users should move
> forward to Stretch (Debian 9.x)
On Sun, Oct 14, 2018 at 10:53:19AM -0700, Noah Meyerhans wrote:
>On Sun, Oct 14, 2018 at 06:02:23PM +0100, Steve McIntyre wrote:
>> One of our (many!) discussion topics at our sprint last week was
>> announcing the end of support for our published Jessie (Debian 8.x)
>> images. We strongly
On Sun, Oct 14, 2018 at 06:02:23PM +0100, Steve McIntyre wrote:
> One of our (many!) discussion topics at our sprint last week was
> announcing the end of support for our published Jessie (Debian 8.x)
> images. We strongly recommend that all our existing users should move
> forward to Stretch
Hey folks,
One of our (many!) discussion topics at our sprint last week was
announcing the end of support for our published Jessie (Debian 8.x)
images. We strongly recommend that all our existing users should move
forward to Stretch (Debian 9.x) to ensure that they have continuing
security
33 matches
Mail list logo
