ote:
>
> Hi Fabrizio,
> We had a discussion on Docker 1.12 but have not proceeded with any
> development yet.
> You are quite welcome to write a blueprint with details on how you envision
> it should work.
> This would help move the discussion along.
> Ton Ngo,
>
> Fabr
Hello,
how about the (newest) Swarm Mode (Docker 1.12+) support in Magnum?
I don’t find any blueprint on Launchpad on the matter yet, is this going to be
worked?
Ta,
Fabrizio.
__
OpenStack Development Mailing List (not for us
Vladimir,
a dedicated repo - good to hear.
Do you have a rough estimate for how long this directory will be in freeze
state?
Thanks,
Fabrizio
> On Feb 15, 2016, at 5:16 PM, Vladimir Kozhukalov
> wrote:
>
> Dear colleagues,
>
> I'd like to announce that we are next to moving fuel-main/virtua
> On Dec 10, 2015, at 12:56 AM, Alvise Dorigo wrote:
>
> So my question is: is there any progress on this topic ? is there a way
> (something like a cronjob script) to make the metadata-agent redundant
> without involving the clustering software Pacemaker/Corosync ?
Reason for such a dirty so
Hello Vladimir, from me -1.
We can discuss if enable fuelmenu=yes or not in grub, but I wouldn't get
rid of it. I've never heard complaints against fuelmenu from users, and
it's widely used for basic settings afterinstall.
If the users had to manually edit another configuration file, should
Lisette, what is this about?
http://it.linkedin.com/in/fsoppelsa
On 06/17/2015 07:10 AM, Lisette Sheehan wrote:
Hi!
I work for an events market research company and am in need of
recruiting young developers in the San Francisco Bay Area to answer a
short survey to see if they qualify for an
+1 definitely
On 03/25/2015 10:10 PM, Dmitry Borodaenko wrote:
Fuelers,
I'd like to nominate Irina Povolotskaya for the fuel-docs-core team.
She has contributed thousands of lines of documentation to Fuel over
the past several months, and has been a diligent reviewer:
http://stackalytics.com/
The proposed monitoring options make sense, since the Fuel master has nothing
yet, but I would like to ressurect this thread to see if we can discuss some
strategies in order to avoid the /var/log fillup with consequent docker
containers corruption.
Now, a customer facing this corruption can re
