Thanks Rick,
CC'ing the openstack-list, based on Vish's request that all openstack
networking discussion be on the main list until we get too chatty and people
want to boot us off :)
I'm as eager as you are to keep the momentum going, but I believe that
during the session on Friday we had agreed
On 05/02/2011 01:19 PM, Dan Wendlandt wrote:
Thanks Rick,
CC'ing the openstack-list, based on Vish's request that all openstack
networking discussion be on the main list until we get too chatty and people
want to boot us off :)
I was planning to forward it to the list as well. That's where
Since the number of projects seems to be increasing daily, I think we
should create a #openstack-meeting schedule page on the wiki, so we
don't accidentally conflict. It would also be a central place to see
what teams are having IRC meetings and when to lurk.
I don't see any real reason to
On May 2, 2011, at 12:50 PM, FUJITA Tomonori wrote:
Hello,
Chuck told me at the conference that lunr team are still working on
the reference iSCSI target driver design and a possible design might
exploit device mapper snapshot feature.
You're involved in the tgt project and it is the tgt
You're involved in the tgt project and it is the tgt project's purgative to
add features as seen fit, but are you sure that you want to support this
feature?
Major spell check fail: prerogative ;-)
Regards,
Eric Windisch
e...@cloudscaling.com
I had a number of discussions with various people at the summit about creating
a forum for openstack (forum.openstack.org) and everyone seemed to think it was
a good idea especially for user support and discussions for people who are not
likely to use a mailing list. So I have 2 questions...
Hello Folks,
I'm still looking for answers to my query below.
Can anybody be able to answer for me ? Thanks in advance.
Cheers,
Shesh
From: openstack-bounces+sheshadri.amathnadu=huawei@lists.launchpad.net
On Mon, May 2, 2011 at 2:45 PM, Eric Windisch e...@cloudscaling.com wrote:
On May 2, 2011, at 12:50 PM, FUJITA Tomonori wrote:
Hello,
Chuck told me at the conference that lunr team are still working on
the reference iSCSI target driver design and a possible design might
exploit
I wish the list archives had a better search function.
On 5/2/11 3:12 PM, Jordan Rinke jor...@openstack.org wrote:
I had a number of discussions with various people at the summit about
creating a forum for openstack (forum.openstack.org) and everyone seemed
to think it was a good idea
1) I think this is a great idea...
2) I would highly recommend XenForo as a platform for the forum
(www.xenforo.com). Check it out if you haven't seen it before. As someone who
moderates a handful of forums and participates on maybe 100+ it is the best
I've seen/used.
-- Chad
On May 2,
I'm all for creating a forum. The Launchpad answers thing is okay but could
be better and it's very siloed to the individual project.
I found a stackexchange-like open source implementation called OSQA: The
Open Source QA System http://www.osqa.net/. It's written in python.
Could be a good fit.
like!
B
On Mon, May 2, 2011 at 3:15 PM, Everett Toews everett.to...@cybera.cawrote:
I'm all for creating a forum. The Launchpad answers thing is okay but could
be better and it's very siloed to the individual project.
I found a stackexchange-like open source implementation called OSQA: The
On 5/2/11 4:03 PM, Matt Dietz matt.di...@rackspace.com wrote:
I think a forum as a means of communication is great. However, I'm not
sure I feel it's the right fit here. My main concern in this regard is
that there would be a separation of important discussions.
I think the class of questions
Fair points. I can see it being used for user support.
Another way to have these sorts of discussions would be an openstack-users
list, but I think lists present much more friction to tire-kickers or
intrigued admins. Forums have a much lower barrier to entry, and
consequently (IMHO) they are
If we create a forum for these types of questions, I suggest we turn off
Questions in Launchpad and direct people to the forum instead. It is already
hard for some people to get a response there and it will only get worse if we
have to answer questions in two places.
Vish
On May 2, 2011, at
On 5/2/11 5:10 PM, Matt Dietz matt.di...@rackspace.com wrote:
Fair points. I can see it being used for user support.
Another way to have these sorts of discussions would be an
openstack-users
list, but I think lists present much more friction to tire-kickers or
intrigued admins. Forums have a
I agree with this posting. One thing to keep in mind is that OpenStack will
have many more users (in other words, people who are not developing the
software, but rather are implementing it or even using someone's implementation
as a basis for end user applications) interested in OpenStack in
It's certainly a matter of personal preference, but I absolutely hate forums.
I hate that I cannot interact with them using clients that I choose.
No, the fact that I can choose between different web browsers doesn't
count. E-mail and usenet, for instance, are excellent means for
communication. I
Hi all.
So what is the decision?
I see three decisions:
#1 Replace existed plain http to ssl
#2 Add additional ports for ssl (save plain http)
#3 Do nothing
Eldar
On Tue, Apr 26, 2011 at 11:27 AM, Dirk-Willem van Gulik
dirk-willem.van.gu...@bbc.co.uk wrote:
On 25 Apr 2011, at 19:47, Kirill
Can we do this with a flag (or two) and just keep regular http if the flag is
not set?
Vish
On May 2, 2011, at 4:34 PM, Eldar Nugaev wrote:
Hi all.
So what is the decision?
I see three decisions:
#1 Replace existed plain http to ssl
#2 Add additional ports for ssl (save plain http)
What I think the essential features for any user support forum are:
1. ability to up vote so the best answers bubble to the top.
2. for the original poster to be able pick the answer they used.
3. the chance to edit answers so they don't become stale.
4. they system searches the forum when you go
On Mon, 2 May 2011 22:41:32 +
Ron Pedde ron.pe...@rackspace.com wrote:
My experience is that I will peruse mailing list archives, but I will
rarely *post* to mailing lists. Something about the formality of it or
the pain of subscribing and unsubscribing (or something!) makes me much
more
On 5/2/11 6:10 PM, Soren Hansen so...@linux2go.dk wrote:
I just know from
experience that try as I might, I'm not likely to maintain any sort of
motivation to participate in forums for any useful amount of time.
And I think that would be the objective of the forums. It doesn't make
sense for
I second Soren's position
- anything which is not streaming into my workflow and does not allow a two
clicks response (Reply/Send) is doomed to stay out of focus and turn into
ignored noise rather than a productivity tool.
Dimitar Boyn
Collaboration Software Group
SaaS Cloud Platform
Hello Barton,
Thanks so much for you reply. Appreciate much. I'll post my questions under QA
next time. Thanks for the tip.
Shesh
From: Barton Satchwill [barton.satchw...@cybera.ca]
Sent: Monday, May 02, 2011 2:31 PM
To: Sheshadri Amathnadu
Cc:
On Mon, 2 May 2011 15:45:20 -0400
Eric Windisch e...@cloudscaling.com wrote:
You're involved in the tgt project and it is the tgt project's
purgative to add features as seen fit, but are you sure that you
want to support this feature?
I'm the maintainer so I can add anything useful unless I
On 05/03/2011 04:12 AM, Jordan Rinke wrote:
I had a number of discussions with various people at the summit about
creating a forum for openstack (forum.openstack.org) and everyone
seemed to think it was a good idea especially for user support and
discussions for people who are not likely to
On 05/03/2011 07:10 AM, Soren Hansen wrote:
I totally understand that I'm reasonably alone in this (the endless
amount of forums with even more endless amounts of users all over the
Internet clearly demonstrates that I'm at least a minority), so don't
let me hold you guys back if you all love
Surely, FUSE is another possible option, I think. I heard that lunr
team was thinking about the approach too.
I'm concerned about the performance/stability of FUSE, but I'm not sure if
using iSCSI is a significantly better option when the access is likely to be
local. If I had to choose
More practical question:
Should we use the same ports for SSL-enabled services as we have for plain-HTTP
now (8773/8774)?
If not, which ones should I choose for my SSL-protected Nova installation?
Of course I can choose any on my own system - the question is - should we agree
which ports will
Is Swift as a Block device a real option? It looks to me that
performance will be a big problem. Also how the three copies of Swift
will be presented as iSCSI? Only one? Each one with its own iSCSI
target? Who serialize the writes in this scenario?
Nelson
On Mon, May 2, 2011 at 6:11 PM, Eric
We should be able to do it with a wsgi middleware and either include
it or not in the paste config file. In a heavily load-balanced
environment you'll probably want to terminate SSL before it gets
proxied to the actual api servers, but it would be nice to support the
simple case where the api
On Mon, 2 May 2011 21:11:22 -0400
Eric Windisch e...@cloudscaling.com wrote:
I expect there will be great demand for an implementation of a Swift
as a block device client. Care should be made in deciding what will
Surely. I also modified tgt to simply store data on Swift. It doesn't
work well
We have no current plans to make an iSCSI target for swift. Not only would
there be performance issues, but also consistency issues among other things.
For Lunr, swift will only be a target for backups from block devices.
I think some of this confusion stems from the confusion around snapshots,
On Mon, May 2, 2011 at 11:48 AM, Rick Clark r...@openstack.org wrote:
Since the number of projects seems to be increasing daily, I think we should
create a #openstack-meeting schedule page on the wiki, so we don't
accidentally conflict. It would also be a central place to see what teams
are
I don't know if a forum is the right answer but I would like to have a
better way to organize information about deployments, operational best
practices and any issues running OpenStack code in production
environments. Maybe the answer is creating a few more mailing
lists and irc channels.
What I've been playing with is having a manifest that contains hashes
of (4mb) chunks for the volume's backups. When a user initiates a new
backup, dm-snapshot does its thing and gives me a block device. I
read and hash chunks from that block device and compare them to the
manifest, uploading
On Mon, May 2, 2011 at 9:12 PM, Michael Barton
mike-launch...@weirdlooking.com wrote:
What I've been playing with is having a manifest that contains hashes
of (4mb) chunks for the volume's backups. When a user initiates a new
backup, dm-snapshot does its thing and gives me a block device. I
38 matches
Mail list logo
