Excerpts from Joshua Harlow's message of 2013-12-06 23:53:47 -0800:
> Agreed,
>
> Chatting earlier today on #cloud-init about all of this I think scott
> convinced me that maybe we (the joint we in the community at large) should
> think about asking ourselves what do we really want a guest agent
On 7 December 2013 21:08, Clint Byrum wrote:
> So what is needed is domain specific command execution and segregation
> of capabilities.
Sounds rather like mcollective.
-Rob
--
Robert Collins
Distinguished Technologist
HP Converged Cloud
___
Open
On Fri, Dec 06, 2013 at 04:30:17PM +0900,
Maru Newby wrote:
> >> 2. A 'best-effort' refactor that maximizes the reliability of the DHCP
> >> agent.
> >>
> >> I'm hoping that coming up with a solution to #1 will allow us the
> >> breathing room to work on #2 in this cycle.
> >
> > Loss of noti
Hi,
We discovered a very serious issue whilst running the CI. The Vmwareminesweeper
would fail due to being unable to schedule instances. The root cause was
incorrect except handling. Would it be possible to please get this into the
stable havana release.
Thanks
Gary
On 7 December 2013 21:53, Isaku Yamahata wrote:
>
> Case 3: Hardware failure. So an agent on the node is gone.
> Another agent will run on another node.
>
> If AMQP service is set up not to lose notification, notifications will be
> piled up
> and stress AMQP service. I would say single n
On Sat, Dec 7, 2013 at 9:08 AM, Clint Byrum wrote:
> So what is needed is domain specific command execution and segregation
> of capabilities.
>
To further this, I know that a lot of security minded people consider this
types of agent sorts of backdoors. Having one generic "backdoor" that can
do
On 12/06/2013 08:55 PM, Clint Byrum wrote:
Excerpts from Jay Pipes's message of 2013-12-06 16:46:24 -0800:
On 12/06/2013 01:38 PM, Clint Byrum wrote:
Excerpts from Jay Pipes's message of 2013-12-05 21:32:54 -0800:
On 12/05/2013 04:25 PM, Clint Byrum wrote:
Excerpts from Andrew Plunk's message
2013/12/6 Alan Pevec :
> 2013/12/4 Alan Pevec :
>> first stable/havana release 2013.2.1 is scheduled[1] to be released
>> next week on December 12th, so freeze on stable/havana goes into
>> effect tomorrow EOD, one week before the release.
>
> We're behind with reviewing so we'll be doing soft-free
Excerpts from Robert Collins's message of 2013-12-07 00:17:19 -0800:
> On 7 December 2013 21:08, Clint Byrum wrote:
>
> > So what is needed is domain specific command execution and segregation
> > of capabilities.
>
> Sounds rather like mcollective.
>
It does actually. If it weren't explicitly
Excerpts from Nicolas Barcet's message of 2013-12-07 01:33:01 -0800:
> On Sat, Dec 7, 2013 at 9:08 AM, Clint Byrum wrote:
>
> > So what is needed is domain specific command execution and segregation
> > of capabilities.
> >
>
> To further this, I know that a lot of security minded people conside
On 12/07/2013 06:48 PM, Clint Byrum wrote:
> Excerpts from Nicolas Barcet's message of 2013-12-07 01:33:01 -0800:
>> On Sat, Dec 7, 2013 at 9:08 AM, Clint Byrum wrote:
>>
>>> So what is needed is domain specific command execution and segregation
>>> of capabilities.
>>>
>>
>> To further this, I
Sounds like a pretty neat idea.
I like it!
Another idea: instead of saying pushing for one agent to rule them all why
don't we come up with a desired reference spec (maybe including a reference
implementation?) that the salt, chef, mcollective, (other...) can base theres
off of. In a way this
Greetings,
I recently enabled multi-domain support on my dashboard and noticed a
new domain context button. I was actually surprised to see I had to
manually toggle the functionality to set the domain context, hiding
domain foo resources from domain bar.
My question is simple, what is the purpos
On 12/07/2013 11:09 PM, Joshua Harlow wrote:
> Sounds like a pretty neat idea.
>
> I like it!
>
> Another idea: instead of saying pushing for one agent to rule them
> all why don't we come up with a desired reference spec (maybe
> including a reference implementation?) that the salt, chef,
> mc
The set domain context functionality is for operators (admins) to refine the
context that they are working in/viewing. Admins can limit the scope of
identity visibility to one domain, rather than having to sort through the
exhaustive lists of projects, users, and groups.
If you are adding mult
On 8 December 2013 17:23, Monty Taylor wrote:
>
> I suggested salt because we could very easily make trove and savana into
> salt masters (if we wanted to) just by having them import salt library
> and run an api call. When they spin up nodes using heat, we could easily
> have that to the cert ex
On 12/08/2013 07:36 AM, Robert Collins wrote:
> On 8 December 2013 17:23, Monty Taylor wrote:
>>
>
>> I suggested salt because we could very easily make trove and savana into
>> salt masters (if we wanted to) just by having them import salt library
>> and run an api call. When they spin up node
17 matches
Mail list logo
