On Mon, Feb 22, 2016 at 8:58 PM, Rene Moser wrote:
> Erik
>
> On 02/22/2016 01:50 PM, Erik Weber wrote:
> > Adding a boilerplate in the install/admin docs that says "If you have no
> > other tools in place to handle system vm updates, consider enabling this
> > option: x.y.z" is good enough for m
bruary 22, 2016 1:39 PM
To: dev@cloudstack.apache.org
Subject: RE: [DISCUSS] Keeping system vms up to date
I think that there are two parts to this - creating system VMs and installing
them.
The systemvms need to have the automated build with versioning 4.5.2-1234 (I'd
like to see that show
Erik
On 02/22/2016 01:50 PM, Erik Weber wrote:
> Adding a boilerplate in the install/admin docs that says "If you have no
> other tools in place to handle system vm updates, consider enabling this
> option: x.y.z" is good enough for me.
> This is supposed to be a way for all those who don't have a
On Mon, Feb 22, 2016 at 1:18 PM, Rene Moser wrote:
> Hi
>
> I don't like the idea cloudstack management handles the "apt-get update
> && apt-get upgrade" (I am -1 for this solution) or at least I would like
> to disable it by configuration, if we go this direction.
>
It should by no means be man
We are comparing different sources, I was comparing the 'official' e.g. the
documented template, not the one regularely built by jenkins.
--
Erik
On Mon, Feb 22, 2016 at 1:11 PM, Remi Bergsma
wrote:
> It _must_ be lying :-)
>
> When I install a systemvm from this last build:
>
> http://jenkin
lieve you have received this email in error.
-Original Message-
From: Nux! [mailto:n...@li.nux.ro]
Sent: Monday, February 22, 2016 9:37 AM
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] Keeping system vms up to date
Hi Erik,
Legit worry point.
IMHO the updates of the VR and so on
Hi
I don't like the idea cloudstack management handles the "apt-get update
&& apt-get upgrade" (I am -1 for this solution) or at least I would like
to disable it by configuration, if we go this direction.
We use ansible (what a surprise) to update the VR and also add some
custom patches to it. We
It _must_ be lying :-)
When I install a systemvm from this last build:
http://jenkins.buildacloud.org/job/build-systemvm64-master/lastBuild/artifact/tools/appliance/dist/systemvm64template-master-4.6.0-xen.vhd.bz2
It has 4.6.0 version, but /etc/cloudstack-version shows it was built today.
cat /
On Mon, Feb 22, 2016 at 11:42 AM, Remi Bergsma
wrote:
> Hi Erik,
>
> The version might not change, but Jenkins builds new ones every night with
> latest OS patches:
> http://jenkins.buildacloud.org/job/build-systemvm64-master/
>
> Option 1) and 3) will work once we allow more space on the systemv
On Mon, Feb 22, 2016 at 10:36 AM, Nux! wrote:
> Hi Erik,
>
> Legit worry point.
>
> IMHO the updates of the VR and so on should be the job of whoever runs the
> cloud, just like it's the same person's job to keep the HVs up to date.
>
Well, to some point I agree, but we should do our best to red
Hi Erik,
The version might not change, but Jenkins builds new ones every night with
latest OS patches:
http://jenkins.buildacloud.org/job/build-systemvm64-master/
Option 1) and 3) will work once we allow more space on the systemvm template
for it to actually handle installing stuff. You then al
Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Erik Weber"
> To: "dev"
> Sent: Monday, 22 February, 2016 08:53:48
> Subject: [DISCUSS] Keeping system vms up to date
> As of 4.6 or so, we don't really need to dist
As of 4.6 or so, we don't really need to distribute new system vm templates
all that often, and that is great for upgrades, but less so from a security
perspective.
With the current approach we ship old system vm templates, with out of date
packages, and there is currently no good out of the box w
13 matches
Mail list logo
