On 09/05/2018 11:48 AM, Jeremy Stanley wrote:
On 2018-09-05 17:01:49 +0200 (+0200), Thomas Goirand wrote:
[...]
In a distro, no 2 package can hold the same file. That's
forbidden. This has nothing to do if someone has to "import
placemement" or not.
Just saying this, but *not* that we should
On 2018-09-05 17:01:49 +0200 (+0200), Thomas Goirand wrote:
[...]
> In a distro, no 2 package can hold the same file. That's
> forbidden. This has nothing to do if someone has to "import
> placemement" or not.
>
> Just saying this, but *not* that we should rename (I didn't spot
> any conflict yet
On 09/04/2018 06:25 PM, Jay Pipes wrote:
> On 09/04/2018 12:17 PM, Doug Hellmann wrote:
>> Excerpts from Jay Pipes's message of 2018-09-04 12:08:41 -0400:
>>> On 09/04/2018 11:44 AM, Doug Hellmann wrote:
Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100:
> On Tue, 4 Sep
On Sep 4, 2018, at 12:44 PM, Chris Dent wrote:
>
> Changing the name, again, is painful. Please, let's not do it.
I was in favor of coming up with a project name for placement. It was
discussed, and the decision was made not to do so. We have since moved forward
with the outcome of that
On Tue, 4 Sep 2018, Jay Pipes wrote:
I wasn't in YVR, which explains why I's never heard of it. There's a number
of misconceptions in the above document about the placement service that
don't seem to have been addressed. I'm wondering if its worth revisiting the
topic in Denver with the
On 09/04/2018 01:17 PM, Balázs Gibizer wrote:
On Tue, Sep 4, 2018 at 7:01 PM, Jay Pipes wrote:
On 09/04/2018 12:59 PM, Balázs Gibizer wrote:
On Tue, Sep 4, 2018 at 6:25 PM, Jay Pipes wrote:
On 09/04/2018 12:17 PM, Doug Hellmann wrote:
Excerpts from Jay Pipes's message of 2018-09-04
On Tue, Sep 4, 2018 at 7:01 PM, Jay Pipes wrote:
On 09/04/2018 12:59 PM, Balázs Gibizer wrote:
On Tue, Sep 4, 2018 at 6:25 PM, Jay Pipes wrote:
On 09/04/2018 12:17 PM, Doug Hellmann wrote:
Excerpts from Jay Pipes's message of 2018-09-04 12:08:41 -0400:
On 09/04/2018 11:44 AM, Doug
On 09/04/2018 12:59 PM, Balázs Gibizer wrote:
On Tue, Sep 4, 2018 at 6:25 PM, Jay Pipes wrote:
On 09/04/2018 12:17 PM, Doug Hellmann wrote:
Excerpts from Jay Pipes's message of 2018-09-04 12:08:41 -0400:
On 09/04/2018 11:44 AM, Doug Hellmann wrote:
Excerpts from Chris Dent's message of
On Tue, Sep 4, 2018 at 6:25 PM, Jay Pipes wrote:
On 09/04/2018 12:17 PM, Doug Hellmann wrote:
Excerpts from Jay Pipes's message of 2018-09-04 12:08:41 -0400:
On 09/04/2018 11:44 AM, Doug Hellmann wrote:
Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100:
On Tue, 4 Sep 2018,
On Tue, 4 Sep 2018, Jay Pipes wrote:
Either one works for me. Though I'm pretty sure that it isn't necessary. The
reason it isn't necessary is because the stuff in the top-level placement
package isn't meant to be imported by anything at all. It's the placement
server code.
Yes.
If some
On 09/04/2018 12:17 PM, Doug Hellmann wrote:
Excerpts from Jay Pipes's message of 2018-09-04 12:08:41 -0400:
On 09/04/2018 11:44 AM, Doug Hellmann wrote:
Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100:
On Tue, 4 Sep 2018, Jay Pipes wrote:
Is there a reason we couldn't have
Excerpts from Jay Pipes's message of 2018-09-04 12:08:41 -0400:
> On 09/04/2018 11:44 AM, Doug Hellmann wrote:
> > Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100:
> >> On Tue, 4 Sep 2018, Jay Pipes wrote:
> >>
> >>> Is there a reason we couldn't have openstack-placement be the
On 09/04/2018 11:44 AM, Doug Hellmann wrote:
Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100:
On Tue, 4 Sep 2018, Jay Pipes wrote:
Is there a reason we couldn't have openstack-placement be the package name?
I would hope we'd be able to do that, and probably should do that.
On 2018-09-04 11:44:41 -0400 (-0400), Doug Hellmann wrote:
> Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100:
[...]
> > I would hope we'd be able to do that, and probably should do that.
> > 'openstack-placement' seems a find pypi package name for a think
> > from which you do
Excerpts from Chris Dent's message of 2018-09-04 15:32:12 +0100:
> On Tue, 4 Sep 2018, Jay Pipes wrote:
>
> > Is there a reason we couldn't have openstack-placement be the package name?
>
> I would hope we'd be able to do that, and probably should do that.
> 'openstack-placement' seems a find
Excerpts from Jay Pipes's message of 2018-09-04 10:05:28 -0400:
> On 09/04/2018 09:37 AM, Jeremy Stanley wrote:
> > On 2018-09-04 09:32:20 +0100 (+0100), Chris Dent wrote:
> > [...]
> >> it allowed for the possibility that there could be another project
> >> which provided the same service-type.
On Tue, 4 Sep 2018, Jay Pipes wrote:
Is there a reason we couldn't have openstack-placement be the package name?
I would hope we'd be able to do that, and probably should do that.
'openstack-placement' seems a find pypi package name for a think
from which you do 'import placement' to do some
On 09/04/2018 09:37 AM, Jeremy Stanley wrote:
On 2018-09-04 09:32:20 +0100 (+0100), Chris Dent wrote:
[...]
it allowed for the possibility that there could be another project
which provided the same service-type. That hasn't really come to
pass
[...]
It still might make sense to attempt to
On 2018-09-04 09:32:20 +0100 (+0100), Chris Dent wrote:
[...]
> it allowed for the possibility that there could be another project
> which provided the same service-type. That hasn't really come to
> pass
[...]
It still might make sense to attempt to look at this issue from
outside the limited
On Tue, 4 Sep 2018, Thomas Goirand wrote:
Just a nit-pick... It's a shame we call it just placement. It could have
been something like:
foo: OpenStack placement
Just like we have:
nova: OpenStack compute
No? Is it too late?
There was some discussion about this on one of the
On 08/31/2018 05:45 PM, Eric Fried wrote:
> The openstack/placement project [1] and its core team [2] have been
> established in gerrit.
>
> I hereby nominate Chris Dent for membership in the placement-core team.
> He has been instrumental in the design, implementation, and stewardship
> of the
21 matches
Mail list logo
