> From: Monty Taylor
> f) Hood is only 4 letters. Think about that when you think about typing
> hatfield a lot. Also, if we name it hatfield, we're going to have to
> have the M summit somewhere that has a town called McCoy.
There's a McCoy in Virginia.
Sorry, but being able to use Hatfield and
when I first created by Wiki id I messed up and I need to erase it to start
over - but I don't see any option to do that. Does someone have a URL to
a page that will let me do that?
thanks
-Doug
STSM | Standards Architect | IBM Softwar
z
To: openstack@lists.launchpad.net,
Date: 11/01/2012 12:33 PM
Subject:Re: [Openstack] summit web site down?
Sent by:openstack-bounces+dug=us.ibm@lists.launchpad.net
Doug Davis wrote:
> I was trying to find the name of the person who ran one of the sessions
> at the San D
I was trying to find the name of the person who ran one of the sessions at
the San Diego summit, but the session [1] doesn't list the name of the
moderator (this would probably be a good thing to require for session
description for the next summit). And so I then thought I might be able to
find
Agreed - the resources used to create a server should be copied into the
server's data if those resources can be deleted (or even modified
independently of the servers using them).
thanks
-Doug
STSM | Standards Architect | IBM Software G
Situations like this are always interesting to watch. :-)
On the one hand its open-source, so if you care about something then put
up the resources to make it happen.
On the other hand, that doesn't mean that as a developer you get to ignore
the bigger picture and only do 1/2 of the work becaus
On the flip side - to refresh people's memory it might be useful to send
out a link to some of the email threads (or wikis) that explained why this
move is critical to OS's success. Perhaps some of those reasons aren't as
valid any more given the impact people are now seeing it will have. Neve
+1 to option 1, rip the band-aid off quickly :-)
-Doug
> -Original Message-
> From: openstack-bounces+gregory_althaus=dell@lists.launchpad.net
> [mailto:openstack-bounces+gregory_althaus=dell.com@lists.launchpad.
> net] On Behalf Of Vishvananda Ishaya
> Sent: Wednesday, July 11, 2012
| IBM 444-6905 | d...@us.ibm.com
The more I'm around some people, the more I like my dog.
Jay Pipes
06/29/2012 06:03 PM
To
Doug Davis/Raleigh/IBM@IBMUS
cc
openstack@lists.launchpad.net, Huang Zhiteng
Subject
Re: [Openstack] Nova and asynchronous instance launching
I'm not e
You don't really expect a client (think ec2-like-user) to analyze debug
info do you?
I really think we need a nice consistent way for people to see what's
going on with long-running operations. Debug info isn't that to me.
thanks
-Doug
__
STS
particular operation.
thanks
-Doug
__
STSM | Standards Architect | IBM Software Group
(919) 254-6905 | IBM 444-6905 | d...@us.ibm.com
The more I'm around some people, the more I like my dog.
Eoghan Glynn
06/29/2012 06:00 AM
To
Doug Davis/Raleigh/IBM@IBMUS
cc
openstack@li
Jay Pipes
Sent by: openstack-bounces+dug=us.ibm@lists.launchpad.net
06/28/2012 12:01 PM
To
openstack@lists.launchpad.net
cc
Subject
Re: [Openstack] Nova and asynchronous instance launching
On 06/27/2012 06:51 PM, Doug Davis wrote:
> Consider the creation of a "Job" type of en
Consider the creation of a "Job" type of entity that will be returned from
the original call - probably a 202. Then the client can check the Job to
see how things are going.
BTW - this pattern can be used for any async op, not just the launching of
multiple instances since technically any op mi
I don't see this as an either-or type of thing.
Totally agree with Mark that the APIs need to be more clearly documented
and that should be independent of any kind of IDL (ala WADL) artifact. I
say this mainly because I think we always need to have something that's
human readable and not mach
__
STSM | Standards Architect | IBM Software Group
(919) 254-6905 | IBM 444-6905 | d...@us.ibm.com
The more I'm around some people, the more I like my dog.
Chris Behrens
06/01/2012 02:42 PM
To
Doug Davis/Raleigh/IBM@IBMUS
cc
Chris Behrens , Matthew Sherborne
, open
Just wondering, is there any reason flavors are not limited to just
create-time? Meaning, use it to create a new instance and then copy all
of the flavor data into the new instance's data. This breaks the
relationship between the instance and the flavor, allow each to be changed
independently
then the CI stuff will detect breakages in the 3rd party APIs right away
and not until some later date when it'll be harder to fix (or undo) those
internal API changes.
-Doug Davis
d...@us.ibm.com___
Mailing list: https://launchpad.net/~openstac
interest.
May not be the easiest thing, but I also don't see it is as that hard
either,
once a decision to explore that option is made. Just my 2 cents...
-Doug Davis
d...@us.ibm.com
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
+1 if you want people to care about something then it should be part of
the main repo and part of the regular regression testing.
thanks
-Doug
__
STSM | Standards Architect | IBM Software Group
(919) 254-6905 | IBM 444-6905 | d...@us.ibm
Mark Nottingham wrote on 04/13/2012 12:56:46 PM:
> In particular, if people are actually using these tools to do data
> binding, it's going to lead them to place dependencies upon the
> structure of our interfaces, and unless the scheme is constructed
> *exactly* right, we'll get lots of bug repor
David Lutterkort wrote:
> A first step to adopting DC in OpenStack would be to bundle DC with the
> OpenStack code (or make sure it's very easy to set up on the widely used
> distros that carry OpenStack). A more involved step would be to write an
> entire OpenStack API frontend that exposes the DC
21 matches
Mail list logo