On 12 October 2015 at 17:16, Sean Dague wrote:
>
> Yes, the last patch was landed on June 16th. We've been running on
> pymysql for most of the liberty development cycle.
Great news! Thanks Sean.
__
Ian Wells wrote:
On 10 October 2015 at 23:47, Clint Byrum > wrote:
> Per before, my suggestion was that every scheduler tries to
maintain a copy
> of the cloud's state in memory (in much the same way, per the previous
> example, as
On 11 October 2015 at 00:23, Clint Byrum wrote:
> I'm in, except I think this gets simpler with an intermediary service
> like ZK/Consul to keep track of this 1GB of data and replace the need
> for 6, and changes the implementation of 5 to "updates its record and
> signals its
Sorry for my lack of explanation.
Are the both scopes of admin and non-admin totally different?
Is each project not nested in admin scope like:
admin {
Some properties
...
{
...
project-a {
owner-a
...
}
project-b {
owner-b
...
}
...
project-x {
On 10/12/2015 08:07 PM, Shinobu Kinjo wrote:
Just question.
Will be scopes of non-admin users projects in admin scoped project?
I'm sorry I don't understand what you are asking.
Shinobu
- Original Message -
From: "Adam Young"
To: "OpenStack Development Mailing
On 10 October 2015 at 23:47, Clint Byrum wrote:
> > Per before, my suggestion was that every scheduler tries to maintain a
> copy
> > of the cloud's state in memory (in much the same way, per the previous
> > example, as every router on the internet tries to make a route table
Excerpts from Ian Wells's message of 2015-10-12 19:43:48 -0700:
> On 11 October 2015 at 00:23, Clint Byrum wrote:
>
> > I'm in, except I think this gets simpler with an intermediary service
> > like ZK/Consul to keep track of this 1GB of data and replace the need
> > for 6, and
101 - 107 of 107 matches
Mail list logo