On Thu, Sep 12, 2013 at 10:08 PM, Monty Taylor wrote:
> And boom, you'll have a directory all set up with your new project
Awesome. I tried it and ran into a couple of small issues. I don't see a
launchpad yet, so I'm not sure where to report bugs.
Something is stripping all the new lines at
On Wed, Jun 19, 2013 at 9:18 AM, Qing He wrote:
> The rationale behind it would be interesting ...
My understanding is that the Quantum corporation (harddrive manufacturer)
asserted
their trademark rights, so the name had to be changed.
See https://lists.launchpad.net/openstack/msg22544.html
I'm moving a thread we had with some vmware guys to this list to make it
public.
We had a problem with quantum deadlocking when it got several requests in
quick
succession. Aaron suggested we set sql_dbpool_enable = True. We did and it
seemed to resolve our issue.
What are the downsides of turn
I haven't closely looked at rootwrap, but it seems to me that you could use
the
rootwrap config files to generate a gigantic sudoers config file which
would not
necessarily be human readable. That would have the flexibility and
maintainability of rootwrap with the speed and audibility sudo.
On T
I've been doing continuous deployment via rpms on RHEL 6u3 of glance,
keystone,
neutron and nova for about six months now. I used Anvil for the first three
months, but it required constant updating of dependency versions and it
didn't
support quantum. Also, yum is terrible at managing dependency
s?? Be interesting to look at
> :-)
>
> From: Jay Buffington
> Reply-To: OpenStack Development Mailing List <
> openstack-dev@lists.openstack.org>
> Date: Monday, August 5, 2013 3:37 PM
> To: OpenStack Development Mailing List
> Subject: Re: [openstack-dev] [De
On Tue, Aug 6, 2013 at 4:36 AM, Ian Wienand wrote:
> On Mon, Aug 05, 2013 at 03:37:24PM -0700, Jay Buffington wrote:
> > I used Anvil for the first three months, but it required constant
> > updating of dependency versions and it didn't support quantum.
>
> What do y
On Tue, Aug 6, 2013 at 8:35 AM, Joshua Harlow wrote:
> I think jay your usage also was before anvil started to build all the
> *missing* dependencies automatically (something u inspired me to get going
> in the first place) so hopefully said updates to rhel.yaml are only now
> needed for exceptio
> Personally I'm of the opinion that from an architectural POV, use of
> either rootwrap or sudo is a bad solution, so arguing about which is
> better is really missing the bigger picture. In Linux, there has been
> a move away from use of sudo or similar approaches, towards the idea
> of having pr
On Tue, Aug 6, 2013 at 12:00 PM, Monty Taylor wrote:
> On 08/06/2013 02:44 PM, Mate Lakat wrote:
> > I would say, use a separated virtual environment in devstack - without
> > the --system-site-packages switch, of course, and set it up as a user.
> > Install the packages that are needed in order
network is layer 2 and subnet is layer 3.
A common use case would be that one tenant creates a network with a
10.1.1.0/24 subnet. Another tenant wants to use that same network, so they
create a new network and can also create the 10.1.1.0/24 subnet.
On Wed, Aug 14, 2013 at 1:12 PM, Lorin Hochst
On Wed, Aug 14, 2013 at 1:41 PM, Jay Pipes wrote:
> On 08/14/2013 04:31 PM, Jay Buffington wrote:
>
>> A common use case would be that one tenant creates a network with a
>>
> 10.1.1.0/24 <http://10.1.1.0/24> subnet. Another tenant wants to use
>> that same netw
We're doing continuous deployment on Oracle Linux 6.3, using a RHEL kernel
making it almost identical to CentOS 6.3. We're using keystone, glance,
neutron and nova. The neutron metadata service doesn't work, nor do
overlapping ips: both need network namespace support in the kernel which
wasn't in
On Fri, Aug 16, 2013 at 2:51 PM, Miller, Mark M (EB SW Cloud - R&D -
Corvallis) wrote:
> Is OpenStack supported on CentOS running Python 2.6?
>
Oh, I forgot to mention, keystone's py2.6 support seems to currently be
broken because of this bug:
https://bugs.launchpad.net/keystone/+bug/1213284/
On Wed, Aug 14, 2013 at 7:12 PM, Robert Collins
wrote:
> Note specifically the citation of 200-400 lines as the knee of the review
> effectiveness curve: that's lower than I thought - I thought 200 was
> clearly fine - but no.
>
This is really interesting. I wish they would have explicitly defin
On Tue, Aug 20, 2013 at 8:02 AM, Mark McLoughlin wrote:
> On Tue, 2013-08-20 at 11:26 +0100, Mark McLoughlin wrote:
>
> The full study is here:
> >
> >
> http://support.smartbear.com/resources/cc/book/code-review-cisco-case-study.pdf
>
I can't find the data they based their numbers on, nor their
16 matches
Mail list logo
