Missing links from this email:
[1]
https://bitbucket.org/hpk42/tox/issues/285/tox-220-breaks-some-toxini-config-files
[2] https://review.openstack.org/#/c/247452/6
On Mon, Nov 23, 2015 at 12:45 PM, Roman Prykhodchenko wrote:
> Hi fulers!
> I’d like to let you know that because of the bug [1] in
Recently we had some cool work done regarding decoupling repositories from
fuel-web. I think it would be really good to have Fuel UI in separate
repository. +1 to the idea.
On Mon, Nov 23, 2015 at 4:56 PM, Roman Prykhodchenko wrote:
> Folks.
>
> This happened again. Nailgun’s API was silently ch
Vitaly,
That's great news. I agree that we need to run fuelclient against every
change in nailgun, but on the other hand - I think we should stick to the
protocol that Igor proposed:
* Announce this change in openstack-dev ML.
* Wait 1 week before approving it, so anyone can prepare.
* Change aut
patch.
Please share your thoughts on this.
Regards,
Maciej Kwiek
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openst
+1
On Mon, Dec 14, 2015 at 3:05 PM, Roman Prykhodchenko wrote:
> Fuelers,
>
> Since Mitaka OpenStack Infra has no resources to test python 2.6 support
> so the corresponding jobs are not running anymore. Since Fuel master node
> is on CentOS 7 now, let’s drop Python 2.6 support in Fuel.
>
>
> -
/var/log?
c) Something else? What?
Please share your thoughts on this.
Cheers,
Maciej Kwiek
[1] https://bugs.launchpad.net/fuel/+bug/1529182
[2]
https://github.com/openstack/fuel-web/blob/2855a9ba925c146b4802ab3cd2185f1dce2d8a6a/nailgun/nailgun/settings.yaml#L717
ll prove
more useful.
Regards,
Maciej Kwiek
[1] https://review.openstack.org/#/c/266964/
On Tue, Jan 12, 2016 at 1:51 PM, Oleg Gelbukh wrote:
> I think we need to find a way to:
>
> 1) verify the size of snapshot without actually making it and compare to
> the available disk space b
an /var. Please see [1] review for a
>> > proposed change that introduces symlinks.
>> >
>> > This doesn't really give us much right now, because most of the logs are
>> > fetched from master node via ssh due to shotgun being run in mcollective
>
esolved into full
> copy?
>
>
> I meant that symlinks also give us the benefit of not using additional
> space (just as hardlinks do) while being able to link to files from
> different filesystems.
>
> I'm sorry, I got you wrong. :)
>
> - Igor
>
> On Thu, Jan 14,
; > targeted snapshots which might also (partially) solve this problem as it
> > would require significantly less disk space to grab logs from a subset of
> > nodes for a specific window of time, instead of the more robust grab-all
> > solution we have now.
> >
> >
&g
b) option :)
>
> b) Make the snapshot location share the diskspace of /var/log?
>
>
> Thanks!
>
> [0] https://bugs.launchpad.net/fuel/+bug/1530131
> [1] https://bugs.launchpad.net/fuel/+bug/1529182
> [2] http://paste.openstack.org/show/484895/
>
>
> On 18.01.16 13
Hi,
I think that checking commit message compliance to commit message
guidelines (for example ending the first line with dot) is part of CI jobs,
and they will vote -1 if message is wrongly structured.
Maybe there should be separate CI job only for checking commit message?
Cheers,
Maciej Kwiek
@Aleksandr: it seems you are right, after my first broken commit message I
was careful not to mess them up again and I didn't even notice that this
check was turned off. Just curious: why was it turned off?
On Wed, Jul 29, 2015 at 11:24 AM, Igor Kalnitsky
wrote:
> Guys,
>
> How do you suppose to
for? We could use their separation to have conflicting versions of
python packages for components that are in separate containers (like
nailgun).
Regards,
Maciej Kwiek
>
>
>
> On Thu, Mar 19, 2015 at 12:01 AM, Dmitry Borodaenko
> wrote:
> > Roman,
> >
> > I like
I guess it would depend on how many docker containers are running on master
node and if we are able to pull off such stunt :).
I am not familiar with the amount of work needed to do sth like that, so
the proposition may be silly. Just let me know if it is.
On Thu, Mar 19, 2015 at 11:51 AM, Dmitry
notification for each node, or can I add one big notification, which
consists of all names of all nodes that failed?
What is the general UI strategy for decisions like that?
Cheers,
Maciej Kwiek
__
OpenStack Development
16 matches
Mail list logo
