Arkady Kanevsky (arkady_kanev...@dell.com) wrote:
> Dell - Internal Use - Confidential
>
> Dell - Internal Use - Confidential
> To help with discussion on branching strategy, enclosed, please, find a
> proposed branching diagram showing currently active and proposed branches
> with their relatio
I just blogged about the tools I wrote for when we forward-ported
stuff from essex-hack-suse to pebbles:
http://blog.adamspiers.org/2013/09/19/easier-upstreaming-with-git/
They could help with roxy and 2.0 too.
___
Crowbar mailing list
Crowbar@dell.c
Vincent Untz (vu...@suse.com) wrote:
> What I'm not happy with is the merge process. I think our current
> process is broken because it's not able to handle the flow of incoming
> pull requests, and when we're trying to compensate this by pushing hard
> we do mistakes like this one.
Agreed! The c
Mike Pittaro (notificati...@github.com) wrote:
> This commit re-organizes the Crowbar Developers Guide.
>
> - Updates to the directory structure.
> - Consolidates a lot of existing documentation from the wiki and
> other locationsin the source tree.
> - Some existing documentation has been conv
Dirk Müller (d...@dmllr.de) wrote:
> Hi Judd,
>
> > There's been some rumblings on our team to split this list into Dev and
> > Users.
> >
> > Have we reached that threshold?
>
> -1. 4 mails a day is not too much.
-1 from me too. Higher traffic on this list is to be encouraged
though :)
_
Dirk Müller (d...@dmllr.de) wrote:
> Hi Scott,
>
> > Although the volume is quite low I think that there are users who are 1)
> > Not comfortable asking basic questions on this list given the technical
> > nature of the discussions the devs are having. 2) When they do ask a
> > question get
Judd Maltin (j...@newgoliath.com) wrote:
> It's come to light that the current manager of the mailing list
> software is no longer available, and that the process of changing the
> list to suit our needs (and any needs that may arise) would take
> months of work.
>
> I'd like to open the discussio
Pittaro, Michael (michael_pitt...@dell.com) wrote:
> On 10/10/2013 12:09 PM, Judd Maltin wrote:
> > It's come to light that the current manager of the mailing list
> > software is no longer available, and that the process of changing the
> > list to suit our needs (and any needs that may arise) wou
Simon Jakesch (simon_jake...@dell.com) wrote:
> On the forum front: Mike is correct, there is a large populous
> preferring forums over mailing lists.
But why? That's what I don't understand. There are countless highly
successful public projects (the Linux kernel, git, and OpenStack to
name just
Judd Maltin (j...@newgoliath.com) wrote:
> FWIW, I like googlegroups, because I can get it via email only, and it
> strips out the _pretty_ *formatting*.
AFAICS it also has the significant disadvantage of only allowing
sending of rich-text messages via the web UI.
Crowbar has one or two JSON-parsing wheels, e.g.
https://github.com/crowbar/barclamp-provisioner/blob/master/updates/parse_node_data
https://github.com/crowbar/crowbar/blob/master/releases/pebbles/master/extra/json-edit
which were already invented elsewhere several times. Take a look at
Shane Gibson (shane_gib...@symantec.com) wrote:
> > -Original Message-
> > Subject: Re: [Crowbar] New Server for Crowbar Lists
> >
> > > > In my experience, users often prefer a forum style interface over a
> > > > mailing list. If we investigate alternatives, I think we should
> > > > con
Ralf Haferkamp (rha...@suse.de) wrote:
> On Sat, Oct 12, 2013 at 01:18:43PM +0100, Adam Spiers wrote:
> > Crowbar has one or two JSON-parsing wheels, e.g.
> >
> >
> > https://github.com/crowbar/barclamp-provisioner/blob/master/updates/parse_node_data
> >
Judd Maltin (j...@newgoliath.com) wrote:
> http://crowbar.sync.in/upstream-cookbooks-planning
>
> I've started with the very basics. I've called out the upstreams, and issues
> I see in both crowbar and upstreams.
>
> This to be filled out much more as the summit commences.
That page is not pu
Thanks, fine now.
Rob Hirschfeld (rob_hirschf...@dell.com) wrote:
> Sorry -fixed.
>
> -Original Message-
> From: crowbar-bounces On Behalf Of Adam Spiers
> Sent: Monday, November 11, 2013 5:10 PM
> To: crowbar
> Subject: Re: [Crowbar] On the matter of upstream
Rob Hirschfeld (rob_hirschf...@dell.com) wrote:
> I believe this was added by Adam a while back to help generate
> coverage stats.
Nope, you're confusing https://github.com/crowbar/ci-tracking with
https://github.com/crowbar/travis-ci-crowbar which was created by
James to allow running of unit tes
Judd Maltin (j...@newgoliath.com) wrote:
> When looking at 'git log' commit messages should have more than a PR #.
I don't quite follow this. Certainly non-merge commits should have
useful commit messages, and following OpenStack's lead in this regard
would be best practice:
https://wiki.open
t;
> Judd Maltin
> 1-917-882-1270
> I have suffering to learn compassion once and once again.
> On Nov 15, 2013 8:38 PM, "Adam Spiers" wrote:
>
> > Judd Maltin (j...@newgoliath.com) wrote:
> > > When looking at 'git log' commit messages should hav
Restructuring the repositories is long overdue, so thank you for
getting behind this. Victor and I discussed it at some length during
my Austin visit, and we documented some of our ideas here:
http://crowbar.sync.in/crowbar-repos
You will see that in addition to restructuring, we mention a
ot;
> Anyone have objections or issues?
I wouldn't be keen on seeing a new org until I'm clear about the
answers to the above questions.
> -Original Message-
> From: crowbar-bounces On Behalf Of Adam Spiers
> Sent: Saturday, November 16, 2013 11:16 PM
> To: crowba
christopher_dearb...@dell.com (christopher_dearb...@dell.com) wrote:
> Rob,
>
> I think you misunderstood my recommendation below. What I'm
> proposing is that we branch everything, including the main Crowbar
> repo.
I think I'm on the same page as you here Chris, although the above
statement mak
Sorry, I don't understand your logic.
Newbie *users* are confused because the website does not contain a
quickly and easily digestible introduction explaining the architecture
and how to get started.
If you need convincing that the website is inadequate, compare it to
https://juju.ubuntu.com/
Judd Maltin (j...@newgoliath.com) wrote:
> Furthermore, since every administrator I talk to asks me "Isn't Crowbar a
> Dell-only project," I think it's a good idea to embrace the OpenCrowbar
> project name.. much as SUSE is recognized by OpenSUSE, even in the press
> http://linux.slashdot.org/story
John Terpstra (john_terps...@dell.com) wrote:
> The fact that Crowbar has a high barrier to new participants is
> undeniable. It is of utmost importance to the future of the project
> that the obstacles to entry of new developers must be removed.
Agreed!
> The positive steps to remove barriers s
Rob Hirschfeld (rob_hirschf...@dell.com) wrote:
> How do we address that CB1 and 2 are so different that the docs can't cover
> both? This seems very confusing to me.
It shouldn't be at all confusing - this is precisely why we started
moving the docs into the code repo, so that whichever branch
Rob Hirschfeld (rob_hirschf...@dell.com) wrote:
> We want to solve those exact problems in CB2 but that creates a huge
> cleanup lift for CB1 that risks CB1 stability.
Sorry - we must have a major disconnect here because I can't
understand this at all. Please can you explain what you mean in more
Simon Jakesch (simon_jake...@dell.com) wrote:
> I've gone through the entire thread and I am going to make an
> attempt at summarizing this conversation to flush out the most
> burning and critical issues around this discussion. I've summarized
> what I believe the high-level argument to be. Please
Darrel O'Pry (darrel.o...@gmail.com) wrote:
> The project has come along way since I first started following it a few
> years ago. What is there now is a vast improvement over what I first found
> which were the links to Rob's blog. It has been steady forward
> progress.
Agreed.
> I hear a lot of
Sascha Peilicke (speili...@suse.com) wrote:
> On the other hand, we could probably kill some branches across
> repos.
Great idea - very low-hanging fruit ... if we are scared about losing
important stuff for ever, we can always take a backup first.
> This is what I currently have just for the "cr
Chux Uzoeto (chuxuzo...@gmail.com) wrote:
> I am fairly new to crowbar .. Thanks to the team for such a great
> concept ..
Welcome :-)
> My question is:
> -- Is there a wiki somewhere about troubleshooting/debugging steps for a
> deployed crowban admin ?
>
> I mean basic information like:
> --
Sascha Peilicke (speili...@suse.com) wrote:
> On Thursday 21 November 2013 08:41:51 Victor Lowther wrote:
> > On Thu, Nov 21, 2013 at 6:33 AM, Adam Spiers wrote:
> > > Sascha Peilicke (speili...@suse.com) wrote:
> > > > I would also wonder why we append
> > >
tion. The below is entirely
separate and relates to the Crowbar project on Ohloh.
- Forwarded message from Steve Snow -
Date: Fri, 22 Nov 2013 11:30:16 -0500
From: Steve Snow
To: Adam Spiers
Subject: Re: Crowbar Project failures
Adam,
I was thinking something just like that. Would real
Steve Snow (ss...@blackducksoftware.com) wrote:
> Folks,
>
> I am assigned to administrative duties at ohloh.net
>
> You will notice some changes at https://www.ohloh.net/p/CrowbarProject
> since we are working through some issues we have been having with
> failures to update our analysis. Withi
I think the problem here is that "move" is a confusing choice of verb,
because Crowbar doesn't really move anything: rather it transforms the
state of those servers. I've fixed the wording.
Simon Jakesch (simon_jake...@dell.com) wrote:
> Matthew,
>
> let me try and answer your questions. In the
Victor Lowther (victor_lowt...@dell.com) wrote:
> Michal,
>
> What is broken for you? I pushed the CB2.0 Ceph stuff I have been
> working on into the mater branch of the ceph repository, is that
> what is causing problems for you?
No, it's that https://github.com/crowbar/barclamp-ceph was not cr
This should help to explain WHY
> someone might want to use Crowbar.
>
> From: crowbar-bounces On Behalf Of Judd Maltin
> Sent: Monday, November 25, 2013 11:08 AM
> To: Adam Spiers
> Cc: crowbar
> Subject: Re: [Crowbar] What is Crowbar exactly?
>
> Might want to say,
As some of you may already know, Symantec evaluated Crowbar 1.6
against Fuel, JuJu/Maas, Foreman, and Rackspace Private Cloud, and
Crowbar won the shoot-out.
They presented their findings at the Hong Kong summit:
http://www.openstack.org/summit/openstack-summit-hong-kong-2013/session-videos/pr
Ah, I see. Is the generation automated? If so, how and where?
There should be a Gemfile to handle the gems required. And we should
really get this working on Ruby 2.0.0 or 1.9.3 at least, since 1.8.7
is absolutely ancient now.
Simon Jakesch (simon_jake...@dell.com) wrote:
> The procedure to up
gave up chasing down the real issue since I actually wanted to push
> an update. I can take another stab at it.
>
> -Original Message-
> From: crowbar-bounces On Behalf Of Adam Spiers
> Sent: Monday, November 25, 2013 12:01 PM
> To: crowbar
> Subject: Re: [Crowba
o, we need to know what version of ceph is this barclamp based on so that
> we can update the crowbar.yml file for our build.
>
>
>
> -Original Message-
> From: crowbar-bounces On Behalf Of Adam Spiers
> Sent: Monday, November 25, 2013 9:33 AM
> To: crowbar
>
John
>
> -Original Message-
> From: crowbar-bounces On Behalf Of Adam Spiers
> Sent: Monday, November 25, 2013 4:50 PM
> To: crowbar
> Subject: Re: [Crowbar] Barclamp-ceph announcement
>
> Sorry, but that won't help. It's not a question of making the refs
--Original Message-
> From: crowbar-bounces On Behalf Of Adam Spiers
> Sent: Tuesday, November 26, 2013 10:03 AM
> To: crowbar
> Subject: Re: [Crowbar] Barclamp-ceph announcement
>
> We already fully understand the problem and know exactly what the resolution
> is - I hav
Darrel O'Pry (darrel.o...@gmail.com) wrote:
> On Thu, Nov 21, 2013 at 6:45 AM, Adam Spiers wrote:
> > Darrel O'Pry (darrel.o...@gmail.com) wrote:
> > > I hear a lot of knee jerk throw everything out and start over undertones.
> > > I
> > > don't
I think the discussion from last week on this list answers your question:
http://lists.us.dell.com/pipermail/crowbar/2013-November/004135.html
Judd Maltin (j...@newgoliath.com) wrote:
> Hi folks,
>
> The github repo is more up-to-date than the website. How can we refresh?
>
> This:
> https://g
Sascha Peilicke (speili...@suse.com) wrote:
> On Sunday 24 November 2013 18:28:18 Victor Lowther wrote:
> > CB 2.0 on opensuse 12.3 with all core Chef roles using the chef-solo jig:
>
> Nice, though we'll likely get bug reports such as "my neck hurts" :-) Any
> chance to render the barclamp names
Comments inline ...
Sascha Peilicke (speili...@suse.com) wrote:
> Hi there,
>
> here's a slightly edited per repository list of branches merged into their
> master branch. All of those are behind master. In other words, those are
> fully
> merged branches waiting to be cleaned up. So if nobody
Simon Jakesch (simon_jake...@dell.com) wrote:
> All,
>
> unfortunately I will not be available for today's meeting. Meeting
> details are available via http://bit.ly/1bgeFoh
That link doesn't work - based on a bit of guesswork I think you meant
http://bit.ly/1bgeF0h ?
___
[Porting conversation from https://github.com/crowbar/crowbar/pull/1959]
Victor Lowther wrote:
> Adam Spiers wrote:
> > On a related note, if we all agree that keeping release-specific stuff
> > in a non-branched repo is highly confusing, then I hope we can also
> > g
Victor Lowther (victor.lowt...@gmail.com) wrote:
> On Wed, Dec 4, 2013 at 3:34 PM, Adam Spiers wrote:
> > [Porting conversation from https://github.com/crowbar/crowbar/pull/1959]
> >
> > gitify-meta breakage follows in case it's of use (BTW this was run
> > immed
Victor Lowther (victor.lowt...@gmail.com) wrote:
> On Wed, Dec 4, 2013 at 3:49 PM, Adam Spiers wrote:
>
> > Victor Lowther (victor.lowt...@gmail.com) wrote:
> > > On Wed, Dec 4, 2013 at 3:34 PM, Adam Spiers wrote:
> > > > [Porting conversation from
> >
Vincent Untz (vu...@suse.com) wrote:
> I initially wanted to summarize where we stand with pull requests, and
> list those that should be okay to go in, and those that need further
> review. But we reached a point where even doing this is just too
> painful: there are 114 pull requests opened right
Hi Sébastien,
Sébastien Braun (sebbr...@gmail.com) wrote:
> Ruby 1.9 removed each method for strings.
>
> But when we provision an admin node, if we edit the ntp-server role
> template to add an NTP server, it will break provisionning. Because when
> trying to use ntp.conf.erb template, it will c
Adam Spiers (aspi...@suse.com) wrote:
> Having said that, in this case, isn't @ntp_servers supposed to be an
> Array of Strings, not a String? Maybe you are editing the proposal
> JSON incorrectly?
Oh, you're talking about Crowbar 2.0. Well, my point still stands:
https:/
Sébastien Braun (sebbr...@gmail.com) wrote:
> Hi Adam,
>
> It's not an Array when bootstrapping the admin node from the Crowbar 2.0
> Web UI, but a string.
>
> When you run the installer with --wizard, you get the opportunity to setup
> things before installing the admin node, when you give a NTP
Iben Rodriguez (iben.rodrig...@gmail.com) wrote:
> Hi Judd,
>
> Most of the larger organizations are using a red hat RHEL or RHEL
> derivative such as CentOS or SuSE, Oracle, Cern, etc.
Just to clarify here:
openSUSE: community distro *not* based on Fedora or RHEL
SLES: SUSE Linux Enter
Hi all,
We have a bit of a confusing situation currently with the docs.
Hopefully this mail will help clarify it.
12 days ago, two pull requests were opened which proposed to move a
bunch of documentation from the main (i.e. top-level) crowbar
repository into the barclamp-crowbar repository:
h
*sigh*
How does duplicating confusion reduce it?
So basically every single one of my unanswered concerns were ignored:
http://thread.gmane.org/gmane.comp.cloud.crowbar/1233/focus=1299
and this was done without any consensus or heads up on this list.
And worse, the new repos have been done wi
Victor Lowther (victor.lowt...@gmail.com) wrote:
> I do not want to go back to having branches in the top-level repo -- I
> strongly prefer that it only hold release-independent (and therefore
> non-branch-needing) things, and pull in other repos that are branched based
> on release.
We agree (as
Judd Maltin (j...@newgoliath.com) wrote:
> Dear Vincent,
>
> I for one do not believe that CB1 is end of life. I think there is still
> good value in the product, strong commit-stream or not. Just the way it is
> it is still far ahead of our nearest competition. It was two years ahead of
> the p
John Terpstra (john_terps...@dell.com) wrote:
> Unfortunately, our internal infrastructure makes use of DevTool to
> build and test CB1.x - if we make the changes Adam suggests will
> take only 60 sec, it will take several engineers from our team to
> update/change/fix the DevTool
No it won't. Th
requirements in the CB1.x code base.
> Having CB2.0 code totally separate from CB1.x means that we all have a green
> field to work from.
>
> - John T.
>
> -Original Message-
> From: crowbar-bounces On Behalf Of Adam Spiers
> Sent: Wednesday, Decem
Rob Hirschfeld (rob_hirschf...@dell.com) wrote:
> Adam,
> As you know, we use a very different build process than your team. We have
> tried several times to duplicate your process using Kiwi and your tool chain
> without success. We are not going to put additional effort into that.
Sure - th
Resending this, since it appears to have been lost amongst the rest of
the discussion:
Adam Spiers (aspi...@suse.com) wrote:
> Even if people disagree with my concerns about a new organization[1],
> surely at very least it would make sense to preserve commit history in
> the transition
Rob Hirschfeld (rob_hirschf...@dell.com) wrote:
> You are correct. I have updated my import process to preserve history.
Fantastic, thanks Rob :)
> While repo histories are preserved (the merged repo has >7 barclamps
> history!), we may not be able to map directly back per file if/as
> they are
Victor Lowther (victor.lowt...@gmail.com) wrote:
> This is intended to work as a starting point for a discussion of what tool
> we should use to use to track inter-repository dependencies for CB2.0 in
> the opencrowbar org.
Before evaluating the tools I think it would be worth trying to
clarify th
Victor Lowther (victor.lowt...@gmail.com) wrote:
> On Fri, Jan 3, 2014 at 5:33 AM, Adam Spiers wrote:
> > Victor Lowther (victor.lowt...@gmail.com) wrote:
> > > This is intended to work as a starting point for a discussion of what tool
> > > we should use to us
Victor Lowther (victor.lowt...@gmail.com) wrote:
> On Fri, Jan 3, 2014 at 8:52 AM, Adam Spiers wrote:
> > Victor Lowther (victor.lowt...@gmail.com) wrote:
> > > On Fri, Jan 3, 2014 at 5:33 AM, Adam Spiers wrote:
> > > > Victor Lowther (victor.lowt...@gmail.com) wro
As requested by Victor, I'd like to start a conversation about the
idea of packaging barclamps as gems (which are then optionally
automatically wrapped in .rpms / .debs). This was first proposed a
*long* time ago by James Tan, and has occasionally surfaced in
conversations since then, but other th
John Terpstra (john_terps...@dell.com) wrote:
> [Uncle] How can we move this forwards? What is the next step and who should
> drive it? How can I help?
I think the next step is addressing any objections that anyone can
come up with ;-)
[snipped]
> Ensuring that all files get copied / moved / sy
Rob Hirschfeld (rob_hirschf...@dell.com) wrote:
> John,
>
> My sense on this is that gems are more for Rails extensions (parts
> of apps) than a full application. While OpenCrowbar is mostly
> Rails, it is NOT only Rails. There's quite a bit of extra stuff
> (chef, erlang, scripts, docs, etc) th
roxy, stoney and hydrogen.
>
>
> Kind regards,
> Thomas Boerger
>
> On Wednesday, December 04, 2013 02:11:50 PM Sascha Peilicke wrote:
> > On Wednesday 04 December 2013 12:32:58 Adam Spiers wrote:
> > > Comments inline ...
> > >
> > > Sascha Pei
Thomas Boerger (tboer...@suse.de) wrote:
> Guys, are you serious? we started this thread multiple months ago and nobody
> really cared about it.
That's not true at all. There was plenty of interest in doing it, but
the final deletion got postponed due to other activities and holidays.
> And now
Thomas Boerger (tboer...@suse.de) wrote:
> On Wednesday, March 12, 2014 11:03:21 AM Adam Spiers wrote:
> > That's not true at all. There was plenty of interest in doing it, but
> > the final deletion got postponed due to other activities and holidays.
>
> Sure it
age-
> From: crowbar-bounces On Behalf Of Thomas Boerger
> Sent: Wednesday, March 12, 2014 9:25 AM
> To: crowbar
> Subject: Re: [Crowbar] Removing branches fully merged into "master".
>
> On Wednesday, March 12, 2014 11:03:21 AM Adam Spiers wrote:
> > That&#x
[BTW no need to send to both crowbar@dell.com and crow...@lists.us.dell.com]
Sascha Peilicke (sasc...@mailbox.org) wrote:
> On the other hand, seasoned developers with an eye for beauty are consistently
> annoyed by the continued over-use of Github.
I'd call it abuse or misuse of git rather than
christopher_dearb...@dell.com (christopher_dearb...@dell.com) wrote:
> Disclaimer: I am not a github expert.
>
> Regarding branch lifecycle:
>
> 1. Work on the release being actively developed continues in a branch
>
> 2. When that release is shipped, another branch is made so that active
ther branch,
> > then it can't be converted to a tag can it?
> >
> >
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Chris
> >
> > Dell
> >
> > -Original Message-
> > From: crowbar-bounces On Behalf
John-Paul Robinson (j...@uab.edu) wrote:
> On 03/18/2014 09:34 PM, Keith Hudgins wrote:
> As a first step, I'm not as interested in add new packages to the nodes
> (that's coming) but more interested in how tune/update the behavior of
> an install service, eg. switch OpenStack to using HTTPS instea
j_t_willi...@dell.com (j_t_willi...@dell.com) wrote:
> Thomas,
> I have received word from our development teams. Here is the view our
> leadership team asserted that we need to address to ensure that we can
> quickly respond and support deployments in the field.
> We should not be taking chanc
John-Paul Robinson (j...@uab.edu) wrote:
> Rob, thanks for the insight on the future direction.
>
> What I really want is some clarification on how to best address these
> issues in the context of an existing Crowbar 1.5 install. I'm
> comfortable getting my hands dirty and retro-fitting capabili
justin_bo...@dell.com (justin_bo...@dell.com) wrote:
> Is the IRC channel dead? I have been reaching out over IRC over the last
> week with no response.
Not quite ;-) But I guess all the Dell guys are busy with Crowbar 2.x
and certainly we (SUSE) are currently busy adding high availability to
th
John-Paul Robinson (j...@uab.edu) wrote:
> Hi,
>
> I'm trying to enable nova client access to my controller deployed by
> crowbar from nodes that are not on the public/float network. In our
> environment the public/float network is a private address range that
> sits behind an additional firewall.
John-Paul Robinson (j...@uab.edu) wrote:
> Do I:
>
> * edit the api.rb in the barclamp-nova under
> /opt/dell/barclamps/nova/chef/cookbooks/nova/recipes/api.rb and then
> install this updated barclamp -- if so how do I install the new
> barclamp?
> * edit the api.rb in the chef conf
Oğuz Yarımtepe (oguzyarimt...@gmail.com) wrote:
> Hi,
>
> I created a new ISO from roxy and realized the new pacemaker barclamp. It
> seems it should be installed first, because when i try skipping it and
> applying the database barclamp i got DRBD related errors.
It needs to be installed, but you
Oğuz Yarımtepe (oguzyarimt...@gmail.com) wrote:
> Hi,
>
> It seems the directories under libraries are not uploaded to chef server:
>
> root@d00-1e-4f-3d-11-fb:/var/cache/chef/cookbooks/pacemaker/libraries# ll
> total 16
> drwxr-xr-x 2 root root 4096 Apr 28 10:55 ./
> drwxr-xr-x 8 root root 4096 Ap
Hi Andrew,
Andrew Brimer (abri...@pearlnet.com) wrote:
> Hello all,
>
> I have created a crowbar iso named
> "crowbar-mesa-1.7_openstack-os-build.3502.dev-ubuntu-12.04"
>
> Once this iso installs the operating system I switch to root and run
> "./install admin.pearlstack.com"
>
> The install fails
Hi Rob,
I'm now getting three copies of every mail to the list(s). I'm not
100% sure but I believe this is because a) mails are being
cross-posted and b) the old list is subscribed to the new list. If
so, in the interests of encouraging a clean migration with minimum
confusion, please can we avo
Hi Siaolé,
Please can you run supportconfig on the Crowbar admin node and make it
available to us somewhere? e.g. you can probably upload to
ftp://ftp.suse.com/pub/incoming
Are you an existing customer, or just evaluating?
Thanks!
Adam
Rob Hirschfeld (rob_hirschf...@dell.com) wrote:
> Siaolé
Gaurav Goyal wrote:
> Dear Dell Team,
I don't believe there is anyone from Dell still involved with Crowbar.
Also, this list is obsolete; the new list is:
https://groups.google.com/forum/#!forum/crowbar
> I am going to use Dell Equallogic iSCSI LUNs with openstack environment.
> Can you pleas
101 - 189 of 189 matches
Mail list logo
