As the former Horizon PTL, I have a great respect for the importance of the
contributions the distro maintainers/developers make to Horizon and OpenStack
as a whole. From how many bugs the distros manage to find, to their diligence
in vetting the software that we as Horizon developers provide,
Good plan, but I really hate the name of this blueprint. I think we
should stop lumping different unrelated HA improvements into a single
blueprint with a generic name like that, especially when we already
had a blueprint with essentially the same name
(ha-pacemaker-improvements). There's nothing
Hi All,
Here’s a summary of what happened at the Summit from the API Working Group
perspective.
Etherpad: https://etherpad.openstack.org/p/kilo-crossproject-api-wg
The 2 design summit sessions on Tuesday were very well attended, maybe 100ish
people I’m guessing. I got the impression there
+1 for ha-pacemaker-improvements
--
Best regards,
Sergii Golovatiuk,
Skype #golserge
IRC #holser
On Fri, Nov 14, 2014 at 11:51 PM, Dmitry Borodaenko
dborodae...@mirantis.com wrote:
Good plan, but I really hate the name of this blueprint. I think we
should stop lumping different unrelated HA
If NTP server is not reachable on the first boot of the master node,
it should be disabled by bootstrap_admin_node, that eliminates the
possibility of it spontaneously coming to life and changing the clock
for fuel master node and all target nodes in the middle of a
deployment. Then all Nailgun
On 11/14/2014 04:01 PM, Dmitry Borodaenko wrote:
If NTP server is not reachable on the first boot of the master node,
it should be disabled by bootstrap_admin_node, that eliminates the
possibility of it spontaneously coming to life and changing the clock
for fuel master node and all target nodes
Oops, the last line should be read as
On the other side, it is a nice UX feature we really want to have 6.0
Dmitry
2014-11-15 3:50 GMT+03:00 Dmitry Mescheryakov dmescherya...@mirantis.com:
Dmitry,
Lets review the CR from the point of danger to current deployment process:
in the essence it
Dmitry,
Lets review the CR from the point of danger to current deployment process:
in the essence it is 43 lines of change in puppet module. The module calls
a shell script which always returns 0. So whatever happens inside, the
deployment will not fail.
The only changes (non-get requests) the
Hello,
As follow-up action after the Design Summit Session on Core/Vendor split,
please find the proposal outlined here:
https://review.openstack.org/#/c/134680/
I know that Anita will tell me off since I asked for reviews on the ML, but
I felt that it was important to raise awareness, even
On 15 November 2014 00:58, Radomir Dopieralski openst...@sheep.art.pl
wrote:
On 14/11/14 13:02, Richard Jones wrote:
I think that it boils down to whether it'is possible that
distributions:
1. package the node-based tools (grunt, karma, protractor, ...) as
installable programs, and
101 - 110 of 110 matches
Mail list logo
