On Wed, Jun 22, 2016 at 6:33 PM, Thierry Carrez
wrote:
> Jeremy Stanley wrote:
>
>> On 2016-06-21 17:34:07 + (+), Jeremy Stanley wrote:
>>
>>> On 2016-06-21 18:16:49 +0200 (+0200), Thierry Carrez wrote:
>>>
It hurts a lot when it's down because of so many services being served
f
Jeremy Stanley wrote:
On 2016-06-21 17:34:07 + (+), Jeremy Stanley wrote:
On 2016-06-21 18:16:49 +0200 (+0200), Thierry Carrez wrote:
It hurts a lot when it's down because of so many services being served from
it. We could also separate the published websites (status.o.o,
governance.o.o
On 06/20/2016 09:22 PM, Jeremy Stanley wrote:
> On 2016-06-08 23:08:16 +1000 (+1000), Joshua Hesketh wrote:
>> On Mon, Jun 6, 2016 at 9:21 AM, Jeremy Stanley wrote:
>> [...]
>>> Store Build Logs in Swift
>> [...]
>>> We should remove the original spec from our priority list (since
>>> that's basic
On 2016-06-21 17:34:07 + (+), Jeremy Stanley wrote:
> On 2016-06-21 18:16:49 +0200 (+0200), Thierry Carrez wrote:
> > It hurts a lot when it's down because of so many services being served from
> > it. We could also separate the published websites (status.o.o,
> > governance.o.o, security.o
On 2016-06-21 18:16:49 +0200 (+0200), Thierry Carrez wrote:
> It hurts a lot when it's down because of so many services being served from
> it. We could also separate the published websites (status.o.o,
> governance.o.o, security.o.o, releases.o.o...) which require limited
> resources and grow slow
Jeremy Stanley wrote:
On 2016-06-21 17:22:15 +1000 (+1000), Joshua Hesketh wrote:
Good update, thanks fungi.
Just a thought, given the pain we felt yesterday when static.o.o was down,
we should consider if a log solution needs to be a priority. Using afs (or
swift) could allow us to scale stati
On 2016-06-21 17:22:15 +1000 (+1000), Joshua Hesketh wrote:
> Good update, thanks fungi.
>
> Just a thought, given the pain we felt yesterday when static.o.o was down,
> we should consider if a log solution needs to be a priority. Using afs (or
> swift) could allow us to scale static.o.o horizonta
Good update, thanks fungi.
Just a thought, given the pain we felt yesterday when static.o.o was down,
we should consider if a log solution needs to be a priority. Using afs (or
swift) could allow us to scale static.o.o horizontally.
On Tue, Jun 21, 2016 at 11:22 AM, Jeremy Stanley wrote:
> On 2
On 2016-06-08 23:08:16 +1000 (+1000), Joshua Hesketh wrote:
> On Mon, Jun 6, 2016 at 9:21 AM, Jeremy Stanley wrote:
> [...]
> > Store Build Logs in Swift
> [...]
> > We should remove the original spec from our priority list (since
> > that's basically already ceased to be an actual priority), and
Thanks for all the updates Jeremy :-)
On Mon, Jun 6, 2016 at 9:21 AM, Jeremy Stanley wrote:
>
>
> Store Build Logs in Swift
> -
>
>
> http://specs.openstack.org/openstack-infra/infra-specs/specs/logs-in-swift.html
>
> This seems to have taken a break, with our log volume
On 07/06/16 00:51, James E. Blair wrote:
With DIB caching, it is generally fairly fast to rebuild a similar image
with 'refreshed' data -- we rely on that for having images with
up-to-date caches of data to keep our runtime short as well.
However, if there truly are images that are not possibl
I'd be happy to look at those issues, so if you can create a story with
tasks
that would be great.
Ricky
2016-06-07 0:42 GMT+02:00 Spencer Krum :
>
> > Ansible Puppet Apply
> >
> >
> >
> http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html
>
On 2016-06-07 00:27:17 +0200 (+0200), Antoine Musso wrote:
> Sorry if I come late in the party, I rely on Nodepool snapshot
> feature to polish up images. I have even hit a wall recently
> attempting to use puppet to provision a service that can not
> always be done in a chroot or be to slow to do
Antoine Musso writes:
> On 06/06/16 01:21, Jeremy Stanley wrote:
>> Use Diskimage Builder in Nodepool
>> -
>>
>> http://specs.openstack.org/openstack-infra/infra-specs/specs/dib-nodepool.html
>>
>> As I understand it, this is complete except for TripleO's images
>>
> Ansible Puppet Apply
>
>
> http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply.html
>
> This seems to be basically done and in production, modulo some bugs
> identified in our session in Austin:
>
> https://etherpad.openstack.org/p/newton-inf
On 06/06/16 01:21, Jeremy Stanley wrote:
Use Diskimage Builder in Nodepool
-
http://specs.openstack.org/openstack-infra/infra-specs/specs/dib-nodepool.html
As I understand it, this is complete except for TripleO's images
(yes, irony since DIB is itself a TripleO
On Mon, Jun 06, 2016 at 03:24:22PM +, Jeremy Stanley wrote:
> On 2016-06-06 10:33:23 -0400 (-0400), Paul Belanger wrote:
> > On Mon, Jun 06, 2016 at 02:26:42PM +, Jeremy Stanley wrote:
> [...]
> > > How long should we wait for possible shrieking before we declare
> > > this done and unlikel
On 2016-06-06 10:33:23 -0400 (-0400), Paul Belanger wrote:
> On Mon, Jun 06, 2016 at 02:26:42PM +, Jeremy Stanley wrote:
[...]
> > How long should we wait for possible shrieking before we declare
> > this done and unlikely to be reverted?
>
> My vote is 3 days. I tested it pretty well so anyth
On Mon, Jun 06, 2016 at 02:26:42PM +, Jeremy Stanley wrote:
> On 2016-06-05 20:15:47 -0400 (-0400), Paul Belanger wrote:
> > On Sun, Jun 05, 2016 at 11:21:47PM +, Jeremy Stanley wrote:
> [...]
> > > Use Diskimage Builder in Nodepool
> > > -
> > >
> > > http:
On 2016-06-05 20:15:47 -0400 (-0400), Paul Belanger wrote:
> On Sun, Jun 05, 2016 at 11:21:47PM +, Jeremy Stanley wrote:
[...]
> > Use Diskimage Builder in Nodepool
> > -
> >
> > http://specs.openstack.org/openstack-infra/infra-specs/specs/dib-nodepool.html
> >
On Sun, Jun 05, 2016 at 11:21:47PM +, Jeremy Stanley wrote:
> Running through the current priorities list (mostly unchanged so far
> from our discussion in Tokyo); let me know if you disagree with
> these observations and we can adjust...
>
>
> Ansible Puppet Apply
>
>
>
On Sun, Jun 05, 2016 at 11:21:47PM +, Jeremy Stanley wrote:
> maniphest migration
> ---
> I think we should swap these in the priority list. However, the
> deployment automation work done for maniphest may still be
> repurposed for pholio (another component of the phabricator
Running through the current priorities list (mostly unchanged so far
from our discussion in Tokyo); let me know if you disagree with
these observations and we can adjust...
Ansible Puppet Apply
http://specs.openstack.org/openstack-infra/infra-specs/specs/ansible_puppet_apply
23 matches
Mail list logo
