Hi guys,
I recently wrote a barclamp to update system packages on deployed nodes.
We will need this for SUSE Cloud to be able to deploy maintenance /
security updates to customers. However, due to the nature of the
barclamp, it isn't supposed to run all time. Instead, a cloud operator
wants to
Sascha Peilicke (speili...@suse.com) wrote:
> Hi guys,
>
> I recently wrote a barclamp to update system packages on deployed nodes.
> We will need this for SUSE Cloud to be able to deploy maintenance /
> security updates to customers. However, due to the nature of the
> barclamp, it isn't suppo
Victor Lowther (victor.lowt...@gmail.com) wrote:
> One of the common pieces of feedback we have gotten is that we do not
> garbage-collect the couchdb databases and views that Chef uses, which
> eventually leads to large amounts of wasted disk space and degraded Chef
> performance.
>
> https://git
Hi Sascha and Adam,
Adam's on the right track with the flag to exit a recipe if it's "one shot."
We do have a script in /opt/dell/bin called on-node, which will
probably also do what you like.
The larger issue, and especially for Crowbar 2.0, is the very nature
of one-shot vs. continuous, eventu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I was wondering what was the reason for this change
https://github.com/crowbar/barclamp-network/commit/a85bb03d7196468c333a58708b42d106d77eaead
but unfortunately the commit message does tell this.
just stumbled over this because our test scrip
Bernard,
192.168.122.1 is used by default by KVM for deployed VM.
I run it on virtual box, but the same issue is on qemu/kvm on linux.
Thus, the easiest solution was NOT to use 122.x IP address range.
Arkady
Original Message-
From: Bernhard M. Wiedemann [mailto:bwiedem...@suse.de]
Sent:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/12/2013 03:51 PM, arkady_kanev...@dell.com wrote:
> Bernard, 192.168.122.1 is used by default by KVM for deployed VM. I
> run it on virtual box, but the same issue is on qemu/kvm on
> linux. Thus, the easiest solution was NOT to use 122.x IP add
Hi,
I just ran "/opt/dell/bin/smoketest tempest" on a built that had the following
pull requests merged:
https://github.com/crowbar/barclamp-glance/pull/82
https://github.com/crowbar/barclamp-quantum/pull/37
https://github.com/crowbar/barclamp-glance/pull/85
https://github.com/crowbar/barclamp-no
On Wed, Jun 12, 2013 at 04:55:08PM +0200, Ralf Haferkamp wrote:
> Hi,
>
[..]
> After "fixing" that. All smoketest up to tempest were executed successfully.
> The tempest test however completely failed. It just repeatedly logged
> something
> like this for all testcases:
>
Team,
Dell had branch off mesa-1.6 off Pebbles.
Reiterating, Pebbles is open for merges since database barclamp changes has
completed.
Arkady
[cid:image001.jpg@01CE676F.46755B10]
Arkady Kanevsky, Ph.D.
Director of SW Development
Enterprise Solution Group
+1 512 723 5264 | arkady_kanev...@de
#7 is done.
BIOS open sourcing is still going on but will be done on pebbles when ready.
Arkady
From: crowbar-bounces On Behalf Of Kanevsky, Arkady
Sent: Monday, June 03, 2013 3:17 PM
To: crowbar
Subject: [Crowbar] status and merge orchestration
Team,
There are a lot of moving parts and we need t
I guess, you cannot run tempest for now on Ubuntu till canonical updates
library.
-Original Message-
From: crowbar-bounces On Behalf Of Ralf Haferkamp
Sent: Wednesday, June 12, 2013 11:24 AM
To: crowbar
Subject: Re: [Crowbar] Is the tempest smoketest supposed to work?
On Wed, Jun 12, 20
Hi,
On Wed, Jun 12, 2013 at 02:27:11PM -0500, arkady_kanev...@dell.com wrote:
> I guess, you cannot run tempest for now on Ubuntu till canonical updates
> library.
Ok, thanks for clarifying. I guess then I can interpret the test results as
succeeded :).
regards,
Ralf
___
I don't think we should remove it in pebbles if it doesn't work (unless
we also believe the option doesn't make sense in general).
Do we have more details about the issue? Is there a bug opened about it?
Vincent
Le mercredi 12 juin 2013, à 12:45 -0700, cdearborn a écrit :
> Merging to pebbles/ma
14 matches
Mail list logo